On 4/7/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> Mark Baker wrote:
> > Gregg,
> >
> > On 4/5/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> > > The issue with REST is that it considers HTTP as the invocation layer
> > too, with
> > > the PUT, GET, POST, etc operations as the fixed set of "functions" that
> > you can
> > > invoke.
> >
> > Right, nicely said.
> >
> > > In a more sophisticated invocation layer, you can imagine the use of
> > > multiple wire protocols such as HTTP being used to perform a single
> > server side
> > > operation.
> >
> > Separating the concerns of application operations and on-the-wire
> > representations had value in CORBA, DCOM, DCE, RMI and other RPC style
> > systems, because they had to support a wide variety of interfaces and
> > operations. But once you embrace a fixed set of operations, the value
> > of keeping these layers separate, drops.
>
> Except when HTTP is not available. That's the issue. Not everything is HTTP
> and not everything works with HTTP.
As Jan said, what I said above doesn't imply HTTP, just uniform
operations. SMTP - email - also has uniform operations, just less of
them than HTTP. i.e. it only has an equivalent for POST ("DATA"), not
of GET, PUT, or DELETE.
> I think your view of "services" is still confined to "transfer a document."
Absolutely.
> This is by far the least common service in my world.
They don't exchange data in your world? Wow, where do you live anyhow? 8-)
It's the most common form of communication used in e-business today (think EDI).
Cheers,
Mark.
--
Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
