This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Atom API?
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Ok, my first question is rather simple - What API?. Yes, there's a draft spec out there. The Draft spec specifies a payload format, but doesn't get into the specifics of how to actually implement a server (or a client). So far as I can tell, I could build a server side implementation in a RESTful fasion, or using url encoded form submissions, or using SOAP. The Blogger folks say they will use SOAP. That's fascinating, but worthless information - because the api names, while specified in the draft (service.post, for instance, is the api for posting) - how you invoke that API would be worthwhile to know. If the spec leaves that open - i.e., if a straight http implementation is as valid as some SOAP implementation, then it's virtually impossible for interested parties (like, say, me) to build a client implementation. Which is why I'm not going to bother until the spec writers figure out what Atom wants to be when it grows up
Previous Topic
