On Mar 5, 2009, at 5:11 PM, Dave Cridland wrote:
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.
I actually think that moving stream management after the bind is a
good thing. Much more flexible, and a relatively minor change.
Sorry, I *knew* something was nagging me about all this...
We also need to deal with S2S sessions,
I didn't get what you said after this, because the first part didn't
really make sense to me. Are you suggesting that we do XEP-198 on S2S
connections? Why bother? They're close enough to stateless that we
shouldn't perturb -198 will new requirements.
While we're on the subject, there are a few changes I'd like to see as
well:
- When the server gives stream features for resumption, it MAY include
a hostname/IP and port on which to reconnect. This allows some
flexibility of deployment.
- Server gives the client a max number of stanzas between
acknowledgements. That way the server can have some control over what
it needs to buffer.
- Server tells the client the maximum amount of time it will keep the
session around after disconnection, in seconds. If the client can't
get reconnected in that timeframe, it can drop its state.
- Clients SHOULD NOT send ack requests back-to-back, without
intervening stanzas.
--
Joe Hildebrand
