Mark Baker wrote: > On 6/28/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote: > >>Humm, but it has been said here that HTTP is an application layer protocol. >>The >>semantics of INVOKE are well defined. A remote reference is indicated in the >>payload which is the service as a URI is in HTTP. The parameters of the >>method >>call are arbitrary, but particular to the service, just like the payload of >>POST >>or PUT. The INVOKE always returns a reply as HTTP does. Help me understand >>what is not uniform about that? > > You have to INVOKE an operation. That operation is the application > layer semantic.
Right, and with HTTP, the message layer semantics that transpire based on you invoking a HTTP operation are at the same level as the eventual method invocation on the remote end of an RMI INVOKE operation. There are no real differentiating factors other than nomenclature here are there? Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> 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/
