はてなブックマーク

The Atom Publishing Protocol is a failure. Now that I've met by blogging-hyperbole-quotient for the day let's talk about standards, protocols, and technology. This is all the fodder I was going to throw together for a presentation I proposed for OSCon. Since that proposal got rejected I'm going to post it here. On the other hand, my App Engine tutorial got accepted, so I'll still see you at the co

The Atom Publishing Protocol Status of this MemoThis document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the “Internet Official Protocol Standards” (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice

Can you explain REST in under 15 minutes? I gave it a try: Very nice explanation indeed, Joe. Thank you very much. I should have tried to fully understand what REST represents some time ago, but always forgot to research, your video is a nice starting point. Now I'm heading to the "Further Reading" items. :) Posted by Gabriel Gilini on 2008-10-08 Great explanation, this will be a worthwhile post t

DeWitt: @dehora Sorry, that should read: We haven't created an AtomPub *for* RPC yet. IMHO, that's the biggest gap today. What we seem to need is a data-oriented REST protocol. We already have document-oriented REST protocols covered with the Atom Publishing Protocol, but what if the information you want to convey is data, i.e. doesn't have the minimum meta-data to qualify as a document, such as a

Update 1: Wow, apparently using Atom as an example was a bad idea given the number of people with their knickers in a twist. Update 2: Fixed the URI Template to accomodate Sam's nose. Update 3: Good feedback from Tim Bray, Mark Nottingham, and Rob Sayre. There are times when you have a large representation of a resource and only want to edit a small part of that resource. Wikipedia is a good examp

The Atom Publishing Protocol draft-ietf-atompub-protocol-17.txt Status of this MemoBy submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Interne

Let's RESTify DayTrader: DayTrader is benchmark application built around the paradigm of an online stock trading system. Originally developed by IBM as the Trade Performance Benchmark Sample, DayTrader was donated to the Apache Geronimo community in 2005. The application allows users to login, view their portfolio, lookup stock quotes, and buy or sell stock shares. Why build a RESTful web service

Everybody's atwitter about WADL, a description file for REST services, and since it's supposed to be RESTful I regularly get questioned about it. For this post I'm going to experiment and adopt Stephen O'Grady's Q&A style. My thanks to Patrick Mueller and Dave Johnson for volunteering to be guinea pigs for my arguments, and thanks to #redmonk for the use of their channel where we initially held th

The Atom Publishing Protocol draft-ietf-atompub-protocol-14.txt Status of this MemoBy submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Interne

The Atom Publishing Protocol draft-ietf-atompub-protocol-13.txt Status of this MemoBy submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Interne

Update (2017): URI Templates are done and now available as RFC6570. Many of the links below may have rotted. I've been working over the past couple months with DeWitt Clinton, Mark Nottingham, Marc Hadley, Dave Orchard, and James Snell on a draft specification for URI Templates, which finally got published yesterday. To provide feedback on this Internet-Draft, join the W3C URI mailing list, and ju

The Atom Publishing Protocol draft-ietf-atompub-protocol-10.txt Status of this MemoBy submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Interne

When asked about the plethora of web frameworks for Python the answer is often that it is way too easy to put together one in Python. That certainly seems plausible since there are so many libraries that implement the components of a web framework and if it's easy to plug those pieces together then maybe that lowers the bar of entry for new frameworks. So let's give it a shot, we'll pick some comp

I've had several conversations recently where it's become clear to me that some people view dynamic languages like Python and Ruby as just Java without the compile step. Yes, one of the advantages of a dynamic language is the ability to drop the compile from the edit/compile/run cycle, but there is much more to it than that. [Update: Some corrections. A first-class function isn't one that is just

There was a conscious decision to not make searching/queries a core part of the APP but to put those in a separate specification, ala OpenSearch. The same can be said of Authentication, it's acknowledged that Basic and Digest aren't cutting it, but creating a new authentication scheme was outside the scope of the AtomPub WG and work is progressing in other venues. The final point is with respect t