[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster-devel] Re: [xmlblaster] Client Failsafe and Re-subscribing

David R Robison wrote:
It is the connection between the Client and the xmlBlaster that is lost. The XML blaster is still running. The client gets notified in the reachedPolling routine. When it reconnects, it is in the reachedAlive routine where I check the session Id. How would I tell if the server has logged me off? I am using version 0.901.
The server emits a logging entry telling you that the client
is logged out.
Further you can do a dump (type 'd' in the server console)
and check if the client is still known.

Please send us more details,


Michele Laghi wrote:

Hi David,
When you say you loose the connection to xmlBlaster, is it the xmlBlaster server which is shutdown or just the connection to it ?

I also would be interested in knowing if the server has logged you off or if it is still pinging. Also tell me which version are you using (please see the additional email on SOCKET PROTOCOL)


David R Robison wrote:

From what I understand from the documentation, if a client re-establishes its connection to the XMLBlaster after polling, then if the returned public session Id is the same as before the connection was lost, then all subscriptions should be intact, otherwise, the subscriptions will need to be restated. I am using the SOCKET protocol and sometimes I see that the subscriptions persist and other times not. Do I understand the documentation correctly? Any thoughts?

David Robison