Based on my reading of the NotificationListener source this is the
sequence that needs to happen (Client and server are both Slide servers
in this case):
1. Client creates a NotificationListener
2. Client subscribes to server with a Subscriber and receives a
subsription id
3a. Client periodically POLLs server for update events for all
subscription ids
AND
3b. Server sends NOTIFY request with a list of subscription ids
to client when a resource is updated
3c. Client POLLs server to get a list of update events for the
notified subscription ids
4. Server returns list of update events for the specified subscription
ids
5. Client calls notify() on the Subscriber registered for each received
update event
6. The subscriber fires a UrisModifiedEvent that is handled elsewhere to
uncache the Uris.
First off, does this sequence of event looks like I'm using
NotificationListener properly?
Second, I'm concerned about the possibility of subscriptions being
dropped if a server goes down. In this scenario if the server where to
restart and lose the subscription id the client would no longer be able
receive events. Is there support for persistent subscriptions on the
server or perhaps a way to notify the client that the subscription was
lost so it can resubscribe?
-James
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
