OpenID23 items tagged “rest”
Versioning REST Web Services. Peter Williams suggests using a vendor MIME media type in the Accept header to specify a required API version, because embedding the API version in the URL itself leads to a single resource ending up with many different URLs, one for each API version. 
13th October 2008, 12:45 pm
RestView—a class for creating a view that dispatches based on request.method (via) I finally got around to writing up a simple approach I’ve been using for REST-style view functions in Django that dispatch based on request.method. 
21st September 2008, 8:47 pm
Dare left something out (and it’s important). Dave Winer: “You should at least learn the lessons and add to REST what it needs to catch up with XML-RPC. Seriously. What’s missing in REST, btw, is a standard method of serializing structs, lists and scalar types.” That would be JSON. 18th August 2008, 9:39 am
Explaining REST to Damien Katz. I didn’t know that it was Mark Baker back in 2002 who first pointed out that SOAP was flawed because it ignored the architecture of the Web as defined by Roy Fielding’s Ph.D thesis. 17th August 2008, 11:19 pm
REST, I just don’t get it. Read the comments for some excellent practical reasons to care about REST, including cache management (PUT and DELETE can expire the cache entries for the corresponding GET), the ability to add or move parts of the server API without redeploying client libraries and the idempotency of GET / PUT / DELETE and HEAD (repeated POST operations may have side-effects). 15th August 2008, 8:20 am
If it’s easy to make all your calls conform to the RESTful verb architecture, then that’s good, I guess. But if not, then just use a POST as an RPC call, keep it as simple as possible and be done with it. And don’t spend another minute worrying about being RESTful or not.
— Damien Katz 15th August 2008, 8:07 am
What is it like to write a technical book? Plenty of food for thought from the lead author of the new edition of High Performance MySQL. It’s amazing how Word is still an integral part of most technical book projects despite its obvious inadequacies compared to a toolchain based on plain text files and Subversion (the Django Book used ReST and Subversion to great effect). 
20th June 2008, 8:18 am
Persevere adds Comet Support. Persevere sounds neat: a RESTful HTTP/JSON data store (the interface reminds me of CouchDB) which recently gained the ability to “subscribe” to a resource and receive notifications of updates via comet. 13th May 2008, 8:09 am
Multi-Inflection-Point Alert. Dammit, Tim, stop giving away our competitive advantages! 26th April 2008, 6:48 pm
I’ve never heard anyone from the REST camp claim that building distributed systems was “easy”. [...] The WS-* folks have historically been obsessed with making things easy, usually for an imaginary business analyst who is nowhere near as technically adept as they. The REST folks, on the other hand, seem much more interested in keeping the entire stack simple, and for everyone involved.
— Ryan Tomayko 13th January 2008, 11:34 pm
A Taxonomy of Event- and REST-based Comet. Kris Zyp describes a conceptual model for Comet messages based on REST semantics (so you can send a PUT referencing a specific URI down to a client to represent an idempotent state change). 21st November 2007, 8:18 pm
[Release] CouchDB 0.7.0. This is a huge milestone for the project—it’s the first official release to include the JSON REST API instead of XML, and it’s also the first release that is “intended for widespread use”. 17th November 2007, 12:25 am
REST plays the same role as open source and open APIs: It eliminates tooling and vendoring as artificial barriers to adoption.
— Assaf Arkin 10th September 2007, 10:58 am
The Python docs have been redesigned for 2.6. They’re beautiful. The docs for a module are on a single page now (rather than splitting over multiple pages), they’ve added unobtrusive permalinks to individual sections and the whole thing is built on ReST rather than LaTeX. 
18th August 2007, 12:39 pm
Wesabi: Your bank has a REST API now. Excellent—I’ve been saying for a while now that I’d really love to be able to program my bank account. 
12th July 2007, 5:20 pm
WS-* is North Korea and REST is South Korea. While REST will go on to become an economic powerhouse with steadily increasing standards of living for all its citizens, WS-* is doomed to sixty years of starvation, poverty, tyranny, and defections until it eventually collapses from its own fundamental inadequacies and is absorbed into the more sensible policies of its neighbor to the South.
— Elliotte Rusty Harold 7th July 2007, 9:40 am
RESTify DayTrader. Killer REST case study from Joe Gregorio. 21st June 2007, 1:44 pm
People don’t recognize how important URIs are. The notion that you have a huge, world-scale, information space, and that everything in it has an name and they’re all just short strings that you can paint on the side of a bus; that’s a new thing and a good thing.
— Tim Bray 2nd May 2007, 8:23 pm
I finally get REST. Wow. “The essence of REST is to make the states of the protocol explicit and addressible by URIs.” 27th April 2007, 4:17 pm
The RADAR Architecture: RESTful Application, Dumb-Ass Recipient (via) Dave Thomas points out that REST expects smart clients, but browsers are dumb (only really support POST and GET). His suggested fix is to build a pure REST service and then drop in a server-side application proxy that sits between the browser and the REST backend. 2nd April 2007, 10:42 am
Highrise Forum: Using the undocumented API. Add .xml to the end of many URLs in Highrise to get an XML representation of that page. 19th March 2007, 11:29 pm
The upshot is that HTTP does not have everything that REST indicates should be present, and there is the additional problem that while HTTP is the first, and best, implementation of REST, the two are not the same and yet are often confused.
— Joe Gregorio 17th February 2007, 5 pm
XML.com: REST on Rails. Matt Biddulph’s Rails mixin provides an instant REST interface to an ActiveRecord model. 4th November 2005, 1:47 pm
