Re: [ws-rx] Usage of Ref parms for WS-Reliable Messaging

[Christopher B Ferris <chrisfer@us.ibm.com>]

Tom,

This would violate the inherent opacity
principle upon which refParams are based because the
server would have to "understand"
that refParam and act accordingly. I would not like to have
RM set a bad precedent.

Cheers,

Christopher Ferris
STSM, Software Group Standards Strategy
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/page/chrisferris
phone: +1 508 377 9295

Tom Rutt <tom@coastin.com> wrote on 09/29/2006
02:32:55 AM:

> 
> quoted from 9/28 minutes:
> 
> "
> Chris: We are not in agreement. I don’t want to use reference params
> because they violate the Web Architecture. WSA WG ignored TAGs issues.
> Paul: I’m not at all in agreement. The reference parameters are not
used 
> to identify a resource, they are used to identify a particular RMD.
> "
> 
> I think that using a ref parm to identify a MakeConnection Queue could
> be considered application level information associated with a particular
> endpoint address.
> 
> I really think, if we wanted to, we could work out a specification
of a 
> use of a ref parm, which when added to the generic wsa:anonymous URI
in 
> the address
> field of an EPR, identifies the "make connection" queue
which will 
> utiize the back channel only when it is appropriate (i.e, when a make
> connection is received with that queue ID).
> 
> What I am trying to say is that only the address is needed for 
> dispatching the message to the appropriate location, and that the
a 
> queueID ref parm could indicate when that anonymous back channel is
> appropriate for use.
> 
> Tom Rutt
> 
> -- 
> ----------------------------------------------------
> Tom Rutt   email: tom@coastin.com; trutt@us.fujitsu.com
> Tel: +1 732 801 5744          Fax: +1 732
774 5133
> 
>