Mark Baker wrote: > On Sat, Sep 17, 2005 at 06:42:33PM -0600, David Forslund wrote: > > If one only as PUT and POST one is severely limited on the type of > > application semantics > > that one can express. Sending all communications over these type of > > "method" calls is > > pretty limiting or requires one to add the application semantics to the > > messages. > > Not at all. Consider that the single method "GET" replaces the need > for all "get*" semantics such as getStockQuote, getInvoice, getName, > getAge, etc ... > > Nothing prevents the *implementation* from varying, it's just the > interface that stays the same, just as getStockQuote can return > both real-time and delayed stock quotes.
But, the way that results are returned, as well as the formatting of those results will create dependencies within your client software. There is no independence from the *implementation* here. The protocol and all of its limitations are embedded in the applications protocol. Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/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/
