Dave Orchard posted a pretty well argued treatise on what is, essentially, a defense of the right for Web services to not adopt the stateless interaction and more importantly, the resource identification constraints which are so important to the Web.
As I explained in my response, if Dave was arguing that Joe Architect should have the right to not follow these constraints (which of course, he already does), he’d have my full support, since in the small, that is often necessary.
However, in the large – when taking into account the value of participating in the information space that is the Web, and of leveraging rather than fighting its network effects – I cannot support him in his attempts to standardize known bad practice, even for non-Web systems.
I won’t bore you with yet another drawn-out description of “why”, since I think I’ve made that clear in the past; the Web is what Web services are trying to be, so why fight it?
no comment until now