On Mon, Jan 19, 2009 at 8:15 AM, Daniel Luebke < [email protected]> wrote:
> Matthieu Riou schrieb: > > [...] > > So how do you typically pass a callback endpoint for a stateful service? > > Also the use case you're describing would probably be better handled > using > > correlation, don't you think? > > > > Cheers, > > Matthieu > > > > I would assume a WS-Addressing replyTo header. The replyTo header > transmits the endpoint reference that is stored in the partnerlink > afterwards. Each invoke and reply by ODE is sent to this new endpoint. > IMO correlation alone does not solve the problem. How does ODE know > where the partner is to be called? Correlation does not deal with > endpoint references. > I was actually going back to your example of a phone number, which is typically stateful information and not just endpoint address. So when you invoke a stateful partner (which a process is) you'll usually need both: something that says which address to call and something that says which instance at that address you're trying to reach. The problem with replyTo in WS-Addressig is that it's explcitly tied to the reply to a request. It's not meant to be kept around and not really fit for long-living asynchronous interactions as we're discussing here. AFAIK there's no standard headers for async endpoint passing. Even less when you want to add stateful information to it. So that's why we had to come up with our own headers. Cheers, Matthieu > > Daniel > > -- > Dr.-Ing. Daniel Lübke > Leibniz Universität Hannover > Welfengarten 1 > D-30167 Hannover > Tel. +49 511 762 19672 > Fax +49 511 762 19679 > > >
