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

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

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Thu, 23 Oct 2003 23:36:13 +0600
Message-ID: <025901c3998c$2a8e5cf0$36356a20@lankabook2>
To: "Umit Yalcinalp" <umit.yalcinalp@oracle.com>
Cc: <www-ws-desc@w3.org>

"Umit Yalcinalp" <umit.yalcinalp@oracle.com> writes:
> I have one "naive" question about your proposal.
> 
> I can envision two different use cases for headers, application specific 
> and middleware introduced. For the latter, one can envision using 
> properties and features (as has been discussed in this thread) and/or 
> specific specs that deal with a specific feature (which is the case 
> today with WS-* specs).
> 
> However, I am not clear on what options we are leaving to applications 
> that would like to define headers. Can you clarify this if we were to 
> remove headers?

In our internal discussions, we've concluded that even when 
applications do introduce headers, that is done as a result of
some policy being applied. Thus, just having a mechanism to 
declare a header isn't enough - one has to say what the 
lifecycle of that header is, what scope it has (not share
across operations, shared across some ops, shared across all
ops etc.). 

In other words, the mechanism in the current draft is woefully
inadequate to describe headers. Extending the functionality is
an option, but I don't think that's a path the WG will like to
go on because it'll dramatically complicate WSDL for everyone.
[Tom, where are you? ;-)]

Hence our proposal that headers be dropped and left in the
domain of policies to introduce and describe the semantics / 
lifecycle of.

My apologies for the delay in replying.

Sanjiva.
Received on Friday, 24 October 2003 13:34:23 GMT

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