Re: [service-orientated-architecture] ROA is not SOA - (was Alternatives to WS Standards)

[Stefan Tilkov]

Hi Dennis,
On Nov 25, 2006, at 2:19 AM, Dennis Sosnoski wrote:

Stefan Tilkov wrote:

On Nov 24, 2006, at 9:15 PM, Dennis Sosnoski wrote:

I agree completely, Paul. POX is clearly the significant alternative to

SOAP, and REST only has as much mindshare as it does because people
mistakenly consider any use of XML over HTTP as REST.

Again, I'm unsure what definition of POX you're using here - POX can
be RESTful or not.

POX *can* be RESTful, but rarely is. The vast majority of POX-type
services I'm aware of (going back to well before SOAP) are based on

(though most use HTTP for this purpose, with POST to send the data to

make of URIs is a URL to identify the service endpoint (a servlet in
Java, or a .aspx in .Net).

exchanging XML documents and don't really care much about the transport the service and get back an XML response irrespective of whether there's any state change on the server at all). In particular, the only use they

Right, there's a vast number of POX implementations that are non- RESTful. But so what? I'm not religious (in any sense) and I don't expect things to follow the ideal all the time. I do claim that the more REST principles are being followed, the better - e.g. it's better to use GET as a "safe" operation, it makes sense to expose resources through URIs, I believe using links in representations is a great idea ... I what problem you see here. Are you arguing that e.g. using a single endpoint URI, or tunneling everything through POST, is *better*? If so, I disagree - this is akin to serializing objects to BLOBs in an RDBMS.

...

I've yet to see any examples of using REST for real service

is going to involve coordinated state changes to many different
"resources". REST appears incapable of dealing with this type of
requirement.

applications. The big problem here is that almost any reasonable service

That's funny because I actually believe that's pretty much what it's
built and being used for :-)

Then let me ask you how to structure an example as a REST service,
Stefan.

[snip]



Stefan
--
Stefan Tilkov, http://www.innoq.com/blog/st/

Interesting example, although I'll need a little more time than I have right now to come up with a decent proposal.

smime.p7s
Description: S/MIME cryptographic signature