I take exception with Dare's title.
For one, Indigo has supported REST from day one. As any true RESTafarian will tell you, REST is an architectural style, not a protocol.
However, for the denomination of REST that equates REST to supporting HTTP PUT and DELETE, the HTTP message transport in Indigo Beta 1 gets in your way, as it is hard wired to POST. We're fixing this, so you can make up HTTP methods until the cows come home (oops - I forgot, there are only four that we'll ever need: PUT/POST/DELETE/GET).
On the POX front, Indigo doesn't force you to use any object mapping/serialization goop nor does it require you to use XSD. Personally, I've been using raw XML access for the past few months and all of your System.Xml skills apply directly.
The XML-based message encoders we ship with Indigo do impose a SOAP envelope around every message. Doug is going to show you how to turn that off.
Indigo is a big tent and needs to support a broad spectrum of users.
Unlike USENET or the blogosphere, there's not much room for religion in product work.
Posted
Jul 14 2005, 09:39 PM
by
don-box