Re: Web Service 'IPersist' Interface?

In case it's not 100% clear, Mark is proposing that you use HTTP's methods
(GET/PUT/POST/DELETE).  Note that the SOAP 1.2 Last Call draft has support
for such methods, though only POST and GET are directly encouraged for
interoperable use at this time.  (Nothing prevents you from building a SOAP
server that deletes SOAP resources in response to a DELETE, however.  It's
a cool thing to do;  it's just that the SOAP bindings do not currently
specify and SOAP faults or processing for DELETE, as they do for POST and
GET.)

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------






                      Mark Baker
                      <distobj@xxxxxxx>        To:       
SOAP@xxxxxxxxxxxxxxxxxxx
                      Sent by:                 cc:       (bcc: Noah 
Mendelsohn/Cambridge/IBM)
                      Discussion of            Subject:  Re: [SOAP] Web Service 
'IPersist' Interface?
                      implementing SOAP
                      applications
                      today
                      <SOAP@xxxxxxxxxxx
                      ELOP.COM>


                      08/20/2002 04:22
                      PM
                      Please respond to
                      Discussion of
                      implementing SOAP
                      applications
                      today






On Tue, Aug 20, 2002 at 12:18:10PM -0700, David Ing wrote:
> If this was 5 years ago I would be reaching for 'IPeristStreamInit' with
> its Load/Save. I know that HTTP intrinsically has its GET/POST verbs but
> we're looking for slightly more, i.e. Create, Load, Save, Update, Remove,
> List, y'know the usual suspects.

You can do those with GET/PUT/POST/DELETE, I believe.

"Create" can be done in one of two ways; if the agent doing the creating
knows the URI, then you can use PUT.  If it doesn't know the URI, and
wants the server to return one, it can POST the data to some container
and then will receive a 201 response with the URI indicated in the
Location header.

"Load" is probably just GET.

"Save" would be PUT, since presumably you know the URI of what it is
you're saving - otherwise use POST as above.

"Update" - is this different than save?

"Remove" would be DELETE.

MB
--
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@xxxxxxx
http://www.markbaker.ca        http://www.idokorro.com

You can read messages from the SOAP archive, unsubscribe from SOAP, or
subscribe to other
DevelopMentor lists at http://discuss.develop.com.

You can read messages from the SOAP archive, unsubscribe from SOAP, or 
subscribe to other
DevelopMentor lists at http://discuss.develop.com.