- From: Christopher B Ferris <chrisfer@us.ibm.com>
- Date: Fri, 13 Dec 2002 16:09:12 -0500
- To: www-ws-arch@w3.org
- Message-ID: <OF5F291EA7.C709B7BC-ON85256C8E.0072B114-85256C8E.00740AE5@rchland.ibm.com>
EXACTLY! Christopher Ferris Architect, Emerging e-business Industry Architecture email: chrisfer@us.ibm.com phone: +1 508 234 3624 www-ws-arch-request@w3.org wrote on 12/13/2002 03:23:43 PM: > > Of course a service may want to restrict what types of documents can go > in and out, > some clients may want to know which types of documents are being dealt > with apriori, > and some providers may want to declare the types of documents they > handle upfront. > Also a client may want to know what is going to happen when a document > is posted. > > Martin. > > > > -----Original Message----- > > From: www-ws-arch-request@w3.org > > [mailto:www-ws-arch-request@w3.org] On Behalf Of Mark Baker > > Sent: Friday, December 13, 2002 10:55 AM > > To: Newcomer, Eric > > Cc: www-ws-arch@w3.org > > Subject: REST and document-oriented Web services > > > > > > > > On Fri, Dec 13, 2002 at 12:31:09PM -0500, Newcomer, Eric wrote: > > > It would seem much more useful to me to compare the > > document oriented > > > style to REST rather than the RPC oriented style. > > > > Ok, REST is the ultimate in document-oriented architectural > > styles. 8-) > > > > You can request (GET) documents, submit (POST) documents to > > document processors, replace documents (PUT), and remove > > documents (DELETE). > > > > MB > > -- > > Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca > > Web architecture consulting, technical reports, evaluation & analysis > > > > >
Received on Friday, 13 December 2002 16:09:48 UTC