On Thu Mar 5 18:19:53 2009, Mickael Remond wrote:
So do we all agree that either way (using jid on resume or starting
stream management after bind), the XEP needs to be modified ?
Not on this basis, no.
Sorry, I *knew* something was nagging me about all this...
We also need to deal with S2S sessions, which have (one or more)
domain-form full jids, and in a cluster it's perfectly reasonable to
have multiple S2S sessions to different nodes from the same domain.
(Unusual, perhaps, but perfectly legal, as far as I can see).
Moreover, the return route may be on a different cluster node than
the inbound route[s], so your routing table might not help at all,
and there *is* no bind.
So I still maintain that you need to figure out the node based purely
on the session id. Of course, that's easily done without worrying
about the full jid at all, you simply need to encode in a node
identifier - that could be the node's address, host, uuid, or
whatever else is convenient.
In summary:
a) The full jid won't always help.
b) There's always something else you can encode into the sm-id to
help you locate the node again.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
