ounds to me as an attempt to compare apples to oranges. I would say it is "unfair" talking about service behavior while dealing with its interface only (WSDL).
I think many people already agree that Web Service and Service are two different things. A Web Service may play a role of a Service interface and WSDL is more or less adequate to the task of an interface description. To define the behavior of the Service for the Services user, aSLA is used. The SAL is supposed to include WSDL and behind-the-interface Service behavior important to particular Services user. As of now, there are a couple SLA descriptive languages are under development.
I think many people already agree that Web Service and Service are two different things. A Web Service may play a role of a Service interface and WSDL is more or less adequate to the task of an interface description. To define the behavior of the Service for the Services user, a
So, when a standardized SLA gets available, would it make sense to continue the discussion Web Services vs. REST?
- Michael Poulin
Mark Baker <[EMAIL PROTECTED]> wrote:
On 7/13/06, Ron Schmelzer <[EMAIL PROTECTED].com > wrote:
>
>
> Hi all --
>
> I've really enjoyed your posts and thoughts on the relationship between SOA, REST, and Web Services. Indeed, we just posted our thoughts on this topic at http://www.zapthink.com/report. I'd love your feedback.html?id=ZAPFLASH -2006712.
Darn it Ron, you were doing so well in that report for the bulk of it,
until you got to this point;
"The fundamental difference, therefore, between REST and
document-style Web Services is how the Service consumer knows what to
expect out of the Service. Web Services have contracts, defined in
WSDL. Since Web Services focus on the Service, rather than on the
resource, the consumer has clear visibility into the behavior of the
various operations of the Service, whereas in REST's resource-oriented
perspective, we have visibility into the resources, but the behavior
is implicit, since there is no contract that governs the behavior of
each URI-identified resource."
Let me ask you this; if you had two service interfaces described by
WSDL, one with a getRealtimeStockQuote operation, and the other with a
getStockQuote operation, would you say the latter's behaviour was more
implicit than the former? I hope your answer would be "No", because
the behaviour isn't implicit, it's just (more) generic. And that's
the same situation with REST.
Mark.
How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates. __._,_.___
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.
