Comments on: Web Architectures and HTTP Mediocrity http://labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/ Sun, 15 Jan 2012 21:29:54 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: bex http://labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/comment-page-1/#comment-140594 bex Tue, 27 May 2008 04:23:55 +0000 http://blog.labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/#comment-140594 "What if queries returned links so you can traverse the graph? What if each resource had both XML and JSON representations? What if you could cache results and not bother processing items unless they changed? What if you could use ETag to update items, detecting and avoiding conflicts?" SOAP can do all of that... just at the application layer, and not the protocol layer. Its no more difficult than creating a convention, then creating applications to conform to that convention. If you want neat-o REST stuff in SOAP, then just compile a list, and come up with the WS-REST specification. “What if queries returned links so you can traverse the graph? What if each resource had both XML and JSON representations? What if you could cache results and not bother processing items unless they changed? What if you could use ETag to update items, detecting and avoiding conflicts?”

SOAP can do all of that… just at the application layer, and not the protocol layer. Its no more difficult than creating a convention, then creating applications to conform to that convention.

If you want neat-o REST stuff in SOAP, then just compile a list, and come up with the WS-REST specification.

]]> By: http://dvae.livejournal.com/ http://labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/comment-page-1/#comment-139452 http://dvae.livejournal.com/ Sun, 06 Jan 2008 19:34:01 +0000 http://blog.labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/#comment-139452 That's it. That's exactly it. Horses for courses. Sometimes you need WS-Security and SAML, and sometimes you need ETags. Just because SOAP and REST are two different ways of sending messages that can be layered on HTTP does mean they work in the same market. So many times I've read 'SOAP sucks'. And yes it does have it's problems, but REST is not an alternative for many things. I have an app where we use WS-Security for encryption and message signing. It's all done in the app server, for now. In a later release we can off load the processing onto off-the-shelf XML security appliances. You can't make those kind of changes with a custom protocol, XMLRPC or REST. WS is the right fit in this case. That’s it. That’s exactly it. Horses for courses. Sometimes you need WS-Security and SAML, and sometimes you need ETags. Just because SOAP and REST are two different ways of sending messages that can be layered on HTTP does mean they work in the same market.

So many times I’ve read ‘SOAP sucks’. And yes it does have it’s problems, but REST is not an alternative for many things.

I have an app where we use WS-Security for encryption and message signing. It’s all done in the app server, for now. In a later release we can off load the processing onto off-the-shelf XML security appliances. You can’t make those kind of changes with a custom protocol, XMLRPC or REST. WS is the right fit in this case.

]]> By: links for 2007-12-18 « Object neo = neo Object http://labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/comment-page-1/#comment-139218 links for 2007-12-18 « Object neo = neo Object Tue, 18 Dec 2007 23:25:49 +0000 http://blog.labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/#comment-139218 [...] Labnotes » Web Architectures and HTTP Mediocrity (tags: soa) [...] [...] Labnotes » Web Architectures and HTTP Mediocrity (tags: soa) [...]

]]>