Re: Web Service 'IPersist' Interface?

Did some more thinking, re-read the SOAP 1.2 draft (esp. the Adjuncts) and
I *do* see what you mean. It's still not quite comfortable in my mind that
I'm using the SOAP HTTP bindings for DELETE, but I like the fact that
they're ubiquitous (which is the point, right?).

I'm straddling Doc-msg style and RPC style, I guess, because
the 'Delete', 'DoWork' etc calls are not 'safe and idempotent' methods. I
feel inconsistent because sometimes I identify the resource via URI and
other times not. This must come up a lot and it would have been nice if 1.2
had specified beyond GET/POST (esp. faults). I also want to re-evaluate
what we've produced already to be more in the spirit of a 'web-architecture
compatible way' (although not today :))

Thank you for your help,
David

On Tue, 20 Aug 2002 16:46:29 -0400, Noah Mendelsohn
<[email protected]> wrote:

>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
>                      <[email protected]>        To:
[email protected]
>                      Sent by:                 cc:       (bcc: Noah
Mendelsohn/Cambridge/IBM)
>                      Discussion of            Subject:  Re: [SOAP] Web
Service 'IPersist' Interface?
>                      implementing SOAP
>                      applications
>                      today
>                      <[email protected]
>                      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.               [email protected]
>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.

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