For those of you who've attended our December UG, you would have heard the proposition from softwaremaker of building web services the REST way. It is definitely an interesting shift and I wonder what's the general opinion of folks out there about this?
A little googling reveals a few interesting articles about this
microlau Blog: http://community.sgdotnet.org/blogs/microlau
REST is nothing but a old-way style of architecture. There will be areas where its better to do REST and there will also be areas where its better to do SOAP/WSDL/WS-*
In any case, WCF (aka Indigo) allows for both. Again, the separation of the technical and functional impediments practised by WCF using System.ServiceModel rules in this sense. You create your [operations] as you usually would. Then decorate your attributes as how you would want to invoke it:
WebHttpBinding with WebHttpBehavior OR WebScriptEnablingBehavior. The former is for a general-purpose behavior that supports UriTemplate dispatch and POX/JSON/byte stream formats on the wire. Use it for general purpose HTTP/REST/Web-Style services. The latter is meant for interop with ASP.NET AJAX clients. It adds in some AJAX-isms like the ability to automatically generate ASP.NET AJAX client proxies.
This article explains this really well: http://www.developer.com/net/article.php/10916_3695436_1
~Softwaremaker (BLOG) M. Twain: "I didn't have time to write a short letter, so I wrote a long one instead"