On Jul 11, 2006, at 3:21 PM, Steve Jones wrote: > On 10/07/06, Mark Baker <[EMAIL PROTECTED]> wrote: > > > > Steve - it is *axiomatic* in REST that all services expose the same > > "operational interface", so yes, we do know that. > > > > http://roy.gbiv.com/pubs/dissertation/rest_arch_style.htm#sec_5_1_5 > > > > Nope, that is the INVOCATION mechanism (the execution context to use > the SOA RM term), that isn't the operational interface that consumers > use. > > With our lightbulb we have > 1) The URI > 2) The data format of the request/response > 3) The meaning of that request/response > > "PUT" is not an operational interface for a service consumer, it is > the execution context that enables the consumer to be connected with > the producer. > Sorry Steve, I am afraid you just have to accept that HTTP indeed does define just that, an operational interface. Or do you really want to suggest that the authors of that spec did not know what they wanted to specify?
I am confused - why do not simply accept what that spec says?? Jan > ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Groups gets a make over. See the new email design. http://us.click.yahoo.com/XISQkA/lOaOAA/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/
