On Mar 6, 2009, at 12:40 PM, Mickaël Rémond wrote:
By harcoding the node in sm-id, who is immutable during the session
you cannot move the session to the node the user is resuming the
session.
So maybe this is the real problem.
If we allow a new sm-id to be set in the middle of a session (maybe in
the <stream:error />), maybe thats a solution for a lot of other use-
cases. For example:
* you decide to gracefully shutdown a node - for each open
connection, send the stream:error with a new sm-id;
* your cluster decides to rebalance some users to another node -
close the connection, include the new sm-id.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: m...@simplicidade.org
Use XMPP!
