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

Re: WebMethod implementation feature

From: Mark Baker <distobj@acm.org>
Date: Tue, 5 Nov 2002 20:15:58 -0500
To: Jacek Kopecky <jacek@systinet.com>
Cc: XMLP Dist App <xml-dist-app@w3.org>
Message-ID: <20021105201558.U1676@www.markbaker.ca>

Yikes, I must have missed this one.

I think that tying the method to the MEP is a bad idea, as I've said
before.  FWIW, I'm (slowly) working on a new HTTP method specification,
"SET", which is like PUT, only more flexible as it allows a processing
model for the content to be introduced.  If you recall, you can't bind
SOAP to PUT and have it do what you expect, because PUT basically means
"store these bits as-is").

If I do this, it would be nice for reasons of reuse to be able to say
that this binding extends the default binding.  But with this resolution
it can't, because the SET binding will also use the Request/Response
MEP, making the MEP->method mapping ambiguous. (there's other reasons,
which I've mentioned before, but this is a new one)

Will the minutes of f2f be posted shortly?


On Tue, Nov 05, 2002 at 06:14:10PM -0500, Jacek Kopecky wrote:
> Hi all, 8-)
> In light of the f2f resolution to issue 294 (see [1]), in particular the
> part that ties the values of WebMethod property to the Message Exchange
> Pattern in use in the HTTP Binding, it seems that the feature #33 in [2]
> is no longer necessary. 
> The reason is, if an implementation supports the HTTP binding and the
> two MEPs, it will use the correct HTTP method regardless of whether or
> not it implements the WebMethod feature.
> The WebMethod feature could be used in a different underlying protocol
> binding, I don't think that our implementation table also covers
> implementations as in "concrete implementations of SOAP 1.2 protocol
> binding framework in particular additional bindings".
> So I think we can remove feature 33 from the implementation features
> table.
> Any thoughts/comments? 8-)
>                    Jacek Kopecky
>                    Senior Architect, Systinet Corporation
>                    http://www.systinet.com/
> [1] http://lists.w3.org/Archives/Public/xmlp-comments/2002Oct/0040.html
> [2] http://www.w3.org/2000/xp/Group/2/03/soap1.2implementation.html

Mark Baker, CTO, Idokorro Mobile.  Ottawa, Ontario, CANADA.
http://www.markbaker.ca             http://www.idokorro.com
Received on Tuesday, 5 November 2002 20:13:42 UTC

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