> If the developer wants [a Foo], then the choice is between requiring
> them to a) have an identifier for the service and understand the
> meaning of the getFoo operation, or b) have an identifier for the
> service. I think it goes without saying that b) is simpler for all
> values of "Foo". So, insofar as HTTP-as-transfer-protocol enables b)
> to happen, while HTTP-as-transport does not, I think the distinction
> matters. Greatly.
That is, perhaps, the most concise explanation that I have ever heard --
I hope you don't mind being quoted? :-)
Cheers,
Elias
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.
