[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebxml-msg] Groups - End-to-end CreateSequence and pulling (ebMS-lastpull-v1.doc) uploaded
my comments inline in red.
On 4 jun 2008, at 02:48, Durand, Jacques R. wrote:
I agree that the sender has to set the address information on the message so that the I-Cloud can route it and knows that the message will be pulled by the receiver. I'm not sure if the mpc that will be used for pulling by the receiver is already in the address information when the message is sent and when it is if there're equal. For example the sender may not know about the pulling and thus setting no mpc or the default one even if the receiver wants to pull the message from a different mpc. This is also related to the subchannel discussion. I think the requirement here is that the intermediary can determine, based on the address information on the message whether it being pulled or not and when it is pulled on which mpc.
I agree, but as you say this is different from the Pull as described and requires different behavior from the endpoints. Consequence is that when you want to use pulling in a multi-hop situation you need to have an MSH implementation that is capable of more than Core V3.
I would however favor this solution!
Agree, but see comment above on Core V3 conformance.
I think the issue of addressing the CSR is now in a separate thread.
I would indeed assume such a mapping