Mike, what I meant by commands in that context was commands in the resource representation, because SOAP, as used with HTTP, is transferred as a resource representation but, as I wrote in other parts of the quoted message, SOAP carries its own commands, at least in the mustUnderstand and understood headers. Hope it's more clear, Jacek Kopecky Senior Architect, Systinet Corporation http://www.systinet.com/ On Thu, 2002-09-05 at 20:41, Mike Dierken wrote: > > > > -----Original Message----- > > > HTTP (and REST) transfers resource representations, a > > term that at least to me doesn't imply any commands. > 'Transfer' is the generalization of /all/ commands specified by HTTP - just > as 'invoke' is the generalization of /all/ commands issued via RPC (of some > kind). > > The HTTP specializes 'transfer' into GET/PUT/POST/DELETE (the 'DELETE' is an > odd one though... 'transfer' might not be generalized enough). > An RPC system would specialize 'invoke' into > 'debitChecking()/transferFunds()/logError()' etc. > > MikeReceived on Friday, 6 September 2002 06:39:43 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:11:52 UTC