Re: [service-orientated-architecture] Zapthink on SOA/REST

[Steve Jones]

Dreadful self plug but....

http://dx.doi.org/10.1109/MS.2005.80 for those of you with IEEE membership.

On 14/07/06, Steve Ross-Talbot <[EMAIL PROTECTED]> wrote:

I'd like to know what constitutes a contract such that it describes the
behavior.
Another point I would make is that a single web service may have several
behaviors for each business process in which it participates and so
behavior
defined from any one services perspective is not an adequate viewpoint
from
which to describe a behavioral contract.

Cheers

Steve T

On 13 Jul 2006, at 23:58, Steve Ross-Talbot wrote:

> The behavior is far from explicit in Web Service because WSDL in and of
> itself does not describe behavior. It only describes the functional
> interface not the order in which functions can be called. The only
> thing that exists today to describe behavior from an architectural
> neutral perspective is WS-CDL and I suspect that isn't what is being
> implied.
>
> Cheers
>
> Steve T
>
> On 13 Jul 2006, at 20:38, Ron Schmelzer wrote:
>
> > Hi Mark --
> >
> > Glad you liked the bulk of it ;) I think you might have missed our
> > point. In Web Services, the behavior is explicit because it's
> defined
> > as such in a contract. In REST, the behavior is implicit because no
> > contract defines what happens when XML is submitted or received as
> > part of a PUT, GET, POST, or DELETE operation.
> >
> > You're right, the two Web Services you mention below have the same
> > level of explicitness. Genericness/granularity is a different
> matter.
> > It might just be that we're using different terms (what's new). I
> mean
> > to say implicit in that someone has to guess what the behavior will
> be
> > or glean it from observing an actual interaction, whereas explicit
> is
> > something declared somewhere in a document or contract.
> >
> > I'm not sure that helps matters, but it might at least explain what
> I
> > meant in that section below.
> > Ron
> >
> > Mark Baker wrote:On 7/13/06, Ron Schmelzer <[EMAIL PROTECTED]>
> > 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.html?id=ZAPFLASH-2006712. I'd love
> >> your feedback.
> >>
> >> 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.
> >>
> >>
> >>
> >> __________ NOD32 1.1658 (20060713) Information __________
> >>
> >> This message was checked by NOD32 antivirus system.
> >> http://www.eset.com
> >>
> >>
> >> __________ NOD32 1.1658 (20060713) Information __________
> >>
> >> This message was checked by NOD32 antivirus system.
> >> http://www.eset.com
> >
> > --
> > __________________________________________________________
> > Ronald Schmelzer
> > [EMAIL PROTECTED]
> > Senior Analyst
> > ZapThink LLC
> > Direct: 781-577-2779 / Main: 781-207-0203
> >
> >
> >
> >
>
>
>

__._,_.___

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.

---

__,_._,___