OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ws-rx] [i089] comments on joint proposal



"Marc Goodner" <mgoodner@microsoft.com> wrote on 06/08/2006 03:12:00 PM:
> > 1- The CS can be carried on the back-channel of a wsrm:
> > MakeConnection, and the CSR on a separate request (in same direction
> > as wsrm:MakeConnection). So it is crucial that both are correlated
> > independently from the underlying protocol. This correlation is
> > needed because of the need to correlate an accept with an offer, and
> > also because the RMS must be able to associate the new seq ID (in
> > CSR) with the address intended by the CS (which is aligned with the
> > address in wsrm:MakeConnection.)
> > How is this correlation done? Is wsa:RelatesTo relied upon? In any
> > case shouldn't this
> > be specified in wsrm as how it is done is critical for interoperability?
>
> Yes the correlation would be done using wsa:RelatesTo.  Not sure we
> need to explicitly say this because this would actually be true of
> any request/response exchange, not just the CS.  Just seems like
> general knowledge these days, no?

>  
> MG:  How does an implementation know whom to direct the response if
> the RelatesTo is for the MakeConnection and not the original
> (potentially blocked) request?  Or does this mechanism require that
> there can only be a single request/response at a time in a sequence?


Marc - in the above scenario the RelatesTo is for the CS not the
MakeConnection.  There is no RelatesTo for the MakeConnection - its a
one-way.

thanks,
-Doug


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]