You know, one of the biggest issues here is over the multi-protocol question. This came up during the recent W3C discussion I've been leading on the "Web of Services" and what, if anything, W3C should do to make it more successful.
(By the way if anyone on this list has any suggestions or input on that, please let me know - or maybe we should start a separate thread? We are still in the middle of this. I have posted several entries about this on my blog and am happy to accept comments there as well.)
Anyway the point is that all Web services specifications are designed for use over multiple communications protocols. So HTTP specific stuff is ruled out by definition. The SOAP envelope is self contained also for this reason - the information needed to process the message has to be included within the message, usually as headers.
This leads to some strange specifications though such as WS-RM, which is basically intended to fix a reliability issue with HTTP, and is not really useful for communication protocols that are already reliable.
In some ways, this continuing debate about REST amounts to a suggestion to use HTTP everywhere and for everything. However as was pointed out during the W3C debate (by users, not vendors by the way) HTTP and URI based protocols are insufficient for use within the firewall. The Web of documents, as REST is usually called within the W3C community, may be great for publishing and distributing corporate data but not so great for updating it or securing access to it.
So even if we were to consider re-inventing UDDI using the Web of documents approach would this be acceptable for inside the firewall deployments? In other words, would the requirement of using HTTP be acceptable for all inside the firewall use of Web services or SOA infrastructure?
Eric
----- Original Message ----
From: Stefan Tilkov <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, June 27, 2006 10:00:11 AM
Subject: Re: [service-orientated-architecture] Re: SOA Reference Architecture
From: Stefan Tilkov <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, June 27, 2006 10:00:11 AM
Subject: Re: [service-orientated-architecture] Re: SOA Reference Architecture
On Jun 27, 2006, at 2:27 PM, Anne Thomas Manes wrote:
> Realistically, though, WS-MEX should be designed as an HTTP GET
> operation rather than a SOAP invocation.
Hear, hear ... next thing you'll know you will suggest to re-invent
UDDI in terms of RESTful HTTP :-)
Stefan
--
Stefan Tilkov, http://www.innoq. com/blog/ st/
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
