MHonArc v2.5.2 -->
ebxml-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [ebxml-msg] RE: The Return Path Problem
Title: RE: [ebxml-msg] RE: The Return Path Problem
Doug.
>>>In the MS specification, we're designing a message routing infrastructure
and have explicitly avoided defining particular routing paradigms. David is
proposing one routing paradigm, others are free to choose something
different. However, going further with David's proposal locks us into a
single method.<<<
I think with the current spec we are already locked into a single method and that is that error messages, delivery messages, etc *have* to be sent back using the same path as the original method was sent. With the current spec Use Case 3 just does not work ! If it can be made to work can someone please explain to me how?
I am also not trying to lock us into a particular proposal. I am only suggesting that we include information from the sending service in a message that is sent that is included in the message that is returned so that it **may** be used for routing purposes when sending a response. I am not suggesting that this information *must* be used for routing.
On the other hand I beleive that Marty is suggesting that *all* routing *has* to be done using the URL and nothing but the URL which, as far as I can see is a single method.
A few more comments below.
David