As subscriptions are WS-Resources, then if you define a persistence method for that resources they should be saved to some kind of storage and loaded when server is restarted. But I'm not a Muse developer so I don't know for sure.
On 12/18/06, Ramesh Gurunathan <[EMAIL PROTECTED]> wrote:
Hi, Is it possible to subscribe to a Topic that is durable? What will happen to a subscription in the event of server crash or an intended shut-down? When the server restarts, would it lose all the subscription data? Since the producer/consumer message exchanges are basically asynchronous in nature, it is very difficult for the client applications to know that its subscription is still active and valid. How to handle such situations? Would the restarted server explain all the subscribers about the sudden or intended death that expired all the subscriptions? I don't like the idea of polling the server to check if the server is still alive and therefore the I believe that I will receive notifications. If the durable subscription isn't possible in Muse, how about adding custom codes? Any suggestions please? Ramesh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Saludos. José Antonio Sánchez --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
