> Because SOAP application semantics are defined by the application and
> hence have nothing to do with HTTP semantics.
That's simply not the case, Sanjiva.
"GET" is as much a "SOAP application semantic" as "getStockQuote".
It's just more generic, that's all; getStockQuote's only good for
stock quotes, but GET is good for stock quotes, weather reports, and
in fact, all information.
It's why HTTP is an *application* protocol ... which has nothing to do
with what those brought up on DCOM and CORBA know as a "protocol",
i.e. "transports".
Mark.
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.
