Jan Algermissen wrote:
> Greg
>
> On Apr 7, 2006, at 3:56 PM, Gregg Wonderly wrote:
>
> > Mark Baker wrote:
> >>
> >> 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.
> >
>
> The architectural constraint of a uniform interface is orthogonal to
> the availability of HTTP. RESTs constraints would induce the same
> properties into your system regardless of the technology you use.
I think we're talking past each other. Please providing me a definition of the
difference between invoking the operation:
int storeInventory( Item items[] );
in RMI verses a REST implementation.
Gregg Wonderly
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/
