W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!)

From: Rich Salz <rsalz@datapower.com>
Date: Tue, 23 Nov 2004 11:25:21 -0500
Message-ID: <41A36471.2030101@datapower.com>
To: Martin Gudgin <mgudgin@microsoft.com>
CC: public-ws-addressing@w3.org

> It depends on how the system is set up. If the EPRs also flow through
> the same proxy, it could automatically record the Qnames of
> RefProps/Params. Alternatively, if the endpoint holds the Qnames of Ref
> Props/Params in a config file, the proxy could use that same config
> file.

Okay, so not only are the contents of RefProps and RefParams opaque, the 
difference between them is intended to be opaque, too.  Is that correct? 
  If so, then this should be called out explicitly in the spec.

But more importantly, if the only entity that can distinguish between a 
prop and a param is the server, then I don't see why the spec has both 
types.  We should be able to drop one (flip a coin:) without any impact 
on the installed base -- servers already have the requisite internal 
config and magic to distinguish between the two -- and greatly simplify 
things.
	/r$
-- 
Rich Salz, Chief Security Architect
DataPower Technology                           http://www.datapower.com
XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html
XML Security Overview  http://www.datapower.com/xmldev/xmlsecurity.html
Received on Tuesday, 23 November 2004 16:17:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:59 GMT