Comments on: Atom too SOAPy for me http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/ Software plumbing using middleware wrenches Sat, 14 Aug 2010 05:26:00 +0000 hourly 1 http://wordpress.com/ By: BigSmoke » Atom and REST http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/#comment-3167 BigSmoke » Atom and REST Tue, 03 Nov 2009 17:23:23 +0000 http://billburke.wordpress.com/?p=141#comment-3167 [...] There’s is an interesting discussion about when (not) to use the Atom protocol for your REST API. [...] [...] There’s is an interesting discussion about when (not) to use the Atom protocol for your REST API. [...]

]]> By: Danny http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/#comment-2438 Danny Fri, 23 Jan 2009 15:48:44 +0000 http://billburke.wordpress.com/?p=141#comment-2438 Hey Bill, I had similar misgivings, but the bottom line is *it ain't RPC*. For passing HTML-ish content around, with rich metadata in the same document, I believe Atom format does the trick. By extension, the atompub protocol works (and avoided the problems of webdav thanks to Fielding's input). I do have doubts about the way collections are defined, but then I'm an RDF head so what do I know. Hey Bill, I had similar misgivings, but the bottom line is *it ain’t RPC*.

For passing HTML-ish content around, with rich metadata in the same document, I believe Atom format does the trick. By extension, the atompub protocol works (and avoided the problems of webdav thanks to Fielding’s input). I do have doubts about the way collections are defined, but then I’m an RDF head so what do I know.

]]> By: Mark Little http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/#comment-2154 Mark Little Wed, 08 Oct 2008 16:17:58 +0000 http://billburke.wordpress.com/?p=141#comment-2154 Yes, I agree with Mic. The best examples of using AtomPub fit into the pub/sub usage as far as I'm concerned. But it'd be very easy to use AtomPub as a "transport" in the same way SOAP uses HTTP and then you're in a completely different world (of pain). Yes, I agree with Mic. The best examples of using AtomPub fit into the pub/sub usage as far as I’m concerned. But it’d be very easy to use AtomPub as a “transport” in the same way SOAP uses HTTP and then you’re in a completely different world (of pain).

]]> By: Location vs. Content-Location at subbu.org http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/#comment-2153 Location vs. Content-Location at subbu.org Tue, 07 Oct 2008 03:12:18 +0000 http://billburke.wordpress.com/?p=141#comment-2153 [...] Here is a quick note on the purposes of and differences between Location and Content-Location response headers. The question came up several times, and more recently in Bill Burke's post on Atom too SOAPy for me. [...] [...] Here is a quick note on the purposes of and differences between Location and Content-Location response headers. The question came up several times, and more recently in Bill Burke's post on Atom too SOAPy for me. [...]

]]> By: Michael Neale http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/#comment-2152 Michael Neale Mon, 06 Oct 2008 22:02:16 +0000 http://billburke.wordpress.com/?p=141#comment-2152 Overreaching with atompub does seem to be a problem - that infoq thread was a good example of that. AtomPub was designed for publishing - so wherever the publish metaphore applies (you have some content, and some meta data that goes with it - and you want to publish it !) I think atompub + REST is a winner. But its all to easy to overgeneralise and treat atompub as a meta data wrapper for SOAP like services. Overreaching with atompub does seem to be a problem – that infoq thread was a good example of that. AtomPub was designed for publishing – so wherever the publish metaphore applies (you have some content, and some meta data that goes with it – and you want to publish it !) I think atompub + REST is a winner. But its all to easy to overgeneralise and treat atompub as a meta data wrapper for SOAP like services.

]]> By: Payload Formats at subbu.org http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/#comment-2151 Payload Formats at subbu.org Mon, 06 Oct 2008 22:01:56 +0000 http://billburke.wordpress.com/?p=141#comment-2151 [...] Bill Burke says: For me, the value of Atom haven’t really clicked with me yet. Its just too SOAPy for me. If you look at ATOM, the ATOM protocol, and how people are talking about using it, they’re really using it as an envelope. One of the things that attracted me to REST was that I could focus on the problem at hand and ignore bulky middleware protocols (like SOAP) and lean on HTTP as a rich application protocol. [...] [...] Bill Burke says: For me, the value of Atom haven’t really clicked with me yet. Its just too SOAPy for me. If you look at ATOM, the ATOM protocol, and how people are talking about using it, they’re really using it as an envelope. One of the things that attracted me to REST was that I could focus on the problem at hand and ignore bulky middleware protocols (like SOAP) and lean on HTTP as a rich application protocol. [...]

]]>