Stale EndpointReferences

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Craig Neuwirt - 14 Sep 2004 13:47 GMT

The WS-Addressing and WS-Messaging support in WSE 2.0 allow exchanging
EndpointReferences between services clients and providers (e.g.
WS-Eventing). Typically, a Web Service may store the EndPointReference in
a database. What is the WS recommended way to handle EndPointReferences
that may be stale because the The Service hosting the endpoint moved to
another machine are is using a different transport. The
EndPointReference.Address is the same, but the EndpointReference.Via is
different. Can WS-Referral somehow help?

thanks,
craig

Reply to this Message

Dilip Krishnan - 15 Sep 2004 03:07 GMT

Craig,
Thats why there is an expiration on the Messages. So when in the
WS-EVenting example, the event subscriber registers for an event it also
sends a time to live for the message
Hth
Regards
Dilip

> The WS-Addressing and WS-Messaging support in WSE 2.0 allow exchanging
> EndpointReferences between services clients and providers (e.g.
[quoted text clipped - 7 lines]
> thanks,
> craig

Reply to this Message

Craig Neuwirt - 15 Sep 2004 14:09 GMT

Dilip,

That is how WS-Eventing avoids a stale NotifyTo reference. What about
the SubscribeManager EndpointReference that is provided to the consumer? My
question is not specific to WS-Eventing, but a general question when
EndpointReferences are exchanged. What if a system is redployed on a new
host and the clients still have EndPointReferences the refer to the old
host? It would be nice to have a feature like the CORBA Location Forward
capbilities.

thanks,
craig

> Craig,
> Thats why there is an expiration on the Messages. So when in the
[quoted text clipped - 15 lines]
> > thanks,
> > craig

Reply to this Message

Stale EndpointReferences

Free Magazines