Skip to main content

Talk: Techniques for Building Third-party RESTful Web Services

I gave a talk today for Py Web SF called "Techniques for Building Third-party RESTful Web Services". Aside from covering a lot of material from the book "RESTful Web Services", I also covered a handful of tips and tricks that I discovered were necessary when creating a third-party RESTful Web Service meant for consumption by Web browsers. Here are the slides in OpenOffice.org format.
Labels:

Comments

Heikki Toivonen said…
While I also use py-restclient, I have a few issues with it. 1) It is more work to override the transport to use something secure (like M2Crypto) than I'd like. 2) I was not expecting it to raise exceptions on non-2XX status codes. I understand the second point is probably a good point for some, but in my case I want to deal with all status codes in a uniform manner, and py-restclient's habit of raising exceptions forces me to translate them back to status codes. 3) It seems like it is also more work than I'd like to make py-restclient use disk cache.
2:37 PM
jjinux said…
Thanks. I haven't used py-restclient, so your comments are helpful. I only mentioned it because Drew Perttula said he really liked it.
3:30 PM
jjinux said…
If you're running OS X, I suggest NeoOffice to open the slides.
12:14 AM
Brent said…
I believe that urllib2 has that same behavior of raising exceptions for non 2xx status codes, so I suspect that py-restclient is using urllib2 (or urllib?) under the hood. I had the same annoyance at urllib2's raising exceptions when using it for a little REST API testing framework I wrote.

The answer, I think, is to go down a level and use httplib directly instead of living with urllib2 and its assumption that all 403s and 404s (for example) should have exceptions raised for them. I've been too lazy to do it yet though. :)
9:10 PM
jjinux said…
Someone at the talk I gave last night also mentioned restkit.

Also, rather than have a script tag load content into a div above the script tag, it's possible to replace the script tag with an automatically generated div.
9:58 PM
metapundit.net said…
Cool talk JJ - the "third party" bit made it very practical.

Apparently the Firefox support for XHR across domains I mentioned is actually a standard. See https://developer.mozilla.org/En/HTTP_access_control and I haven't checked to see what other modern browsers do/will support it.
10:11 PM
jjinux said…
Thanks, Simeon.
10:50 PM
Unknown said…
Clicking on the "here are the slides" link I get a 404:

404 Not Found
The server can not find the requested page:

ironorchid.com/jjinux/articles/restful_web_services/slides.odp (port 80)
Please forward this error screen to ironorchid.com's WebMaster.
10:40 AM
jjinux said…
Sorry about that. My buddy must have stopped paying for hosting. Try this.
1:33 AM
Post a Comment

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe
1 comment
Read more

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo
50 comments
Read more

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p
66 comments
Read more