tmpreiss commented on May 9, 2016
We need some logic in the client SDKs that re-issues a sub if the server has dropped it, e.g. if the client has been disconnected long enough that the rabbit queues are dropped. If the client gets disconnected and on reconnect is told it has created a new session, then it should re-issue the sub for any outstanding listens.
We also need to add logic in the server to notify the client when the session has been recreated (as opposed to simply reconnected).
@mkistler responded:
"I believe we can manage this entirely in the clients by reissuing subs whenever a connection is re-established. Since the server does not reference-count sub's, these have no affect when the session is still alive but will re-establish the sub when the session timed out."
tmpreiss commented on May 9, 2016
We need some logic in the client SDKs that re-issues a sub if the server has dropped it, e.g. if the client has been disconnected long enough that the rabbit queues are dropped. If the client gets disconnected and on reconnect is told it has created a new session, then it should re-issue the sub for any outstanding listens.
We also need to add logic in the server to notify the client when the session has been recreated (as opposed to simply reconnected).
@mkistler responded:
"I believe we can manage this entirely in the clients by reissuing subs whenever a connection is re-established. Since the server does not reference-count sub's, these have no affect when the session is still alive but will re-establish the sub when the session timed out."