W3C home > Mailing lists > Public > www-ws-desc@w3.org > October 2003

RE: PROPOSAL: Drop interface/operation/(input|output)/@headers

From: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
Date: Tue, 28 Oct 2003 17:47:47 -0800
Message-ID: <DDE1793D7266AD488BB4F5E8D38EACB8038DC8AD@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
To: "Glen Daniels" <gdaniels@sonicsoftware.com>, "Roberto Chinnici" <Roberto.Chinnici@Sun.COM>, "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
Cc: <www-ws-desc@w3.org>

> From: Glen Daniels
> 
> Correct.  Essentially, the only kinds of headers that are worth
specifying
> with the mechanism that exists today are the "cookie-esque" ones -
i.e.
> "please send me the value 'xq57jb' back in the header
'myns:SeekritCode'.
> Oh, and send it on every single message, too."  Anything with more
complex
> semantics than that can't really be accommodated with the current
syntax.
> So I think it's a pretty simple matter to define a "sideband data"
SOAP
> module which simply takes a property consisting of a set of elements,
and
> inserts them as SOAP headers.

Do you see any value in allowing the WSDL to specify actor/role,
mustUnderstand, and/or relay for such 'cookie-esque' header blocks?

--Jeff
Received on Tuesday, 28 October 2003 20:47:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:27 GMT