W3C home > Mailing lists > Public > xml-dist-app@w3.org > July 2002

RE: FW: LC Comments: Web Method Feature

From: Williams, Stuart <skw@hplb.hpl.hp.com>
Date: Wed, 3 Jul 2002 17:27:02 +0100
Message-ID: <5E13A1874524D411A876006008CD059F04A06EF8@0-mail-1.hpl.hp.com>
To: "'Mark Baker'" <distobj@acm.org>, Marc Hadley <marc.hadley@sun.com>
Cc: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>

> -----Original Message-----
> From: Mark Baker [mailto:distobj@acm.org]
> Sent: 03 July 2002 15:13
> To: Marc Hadley
> Cc: 'xml-dist-app@w3.org'
> Subject: Re: FW: LC Comments: Web Method Feature
> Marc,
> I think my response to Stuart should answer your first question.
> On Wed, Jul 03, 2002 at 01:24:54PM +0100, Marc Hadley wrote:
> > All good questions. I don't think the MEP and web method feature (as 
> > currently formulated) are particularly orthogonal. I wonder if a better 
> > formulation might be to add an optional "safe" feature instead of the 
> > existing web method feature such that the HTTP binding will use GET only

> > when the MEP is response and the "safe" feature is set ?
> While GET is safe, not all safe methods are GET.  For example, HEAD is
> safe.

From [1]:


     In HTTP, GET must not have side effects.

  The introduction of any other method apart from GET which has no side
  effects is also incorrect, because the results of such an operation 
  effectively form a separate address space, which violates the

...care to comment?
> I have to admit to being confused by the suggestions to derive the
> method.  Why is that desirable? 

Well we continue to have the two views... the chameleon view and the
messaging/tunneling view. 

We are close to a position that admits both views. The Web Method features
enables the chameleon to take on the REST resource state manipulation and
retrieval view. Mandating its use (needlessly IMO) denies the
messaging/tunneling view.

> A developer has to know what methods are being invoked.  How else can they
get their job done?

Developers of binding implementations will know... the binding specification
will tell them.

Developers of SOAP applications will know the semantics of the features they
use, because the feature specification will tell them. If the resource state
view is important to them, they will use the Web Method feature. If they
think more in terms of message exchange (in a binding agnostic fashion) Web
Method is unlikely to be a feature they will use.

Developers of Soup to Nuts homogeneous implementations will likely
streamline their implementations based on their understanding of the
agregate behaviour of their application and the features and bindings it
actually uses.

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


[1] http://www.w3.org/DesignIssues/Axioms.html#state
Received on Wednesday, 3 July 2002 12:29:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:20 UTC