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. In fact, we as an industry have found considerable value in making these layers more cohesive. One of the main benefits is performance; with fixed operations, you can optimize the lower layer stuff for the operations themselves. Indeed, HTTP is a great example of that; consider that many of its features wouldn't need to exist if it didn't have a GET operation. In other words, implementing "GET" as an IDL operation over IIOP will, for a typical document exchange scenario, be faster using HTTP, despite HTTP being text and IIOP being binary. 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/
