Dave Cridland wrote:
On Fri Mar 6 06:39:19 2009, Curtis King wrote:
The xep needs some filling out or maybe be split into two separate
xeps. IMHO, resuming a session is only useful for C2S connections.
Why bother with S2S connections.
Resuming S2S sessions is mostly concerned with reliability, rather than
optimization. It means that servers can avoid any stanza-loss due to a
connection drop. (In principle, this shouldn't be possible now, but in
practice, it seems to happen on occasion).
And did anyone ever investigate why this happens? I doubt that the
majority of those 'lost stanzas' is physically lost. Incorrect handling
of 'bounces' when a S2S connection does not get established for some
reason seems much more likely to me.
For example:
<presence type='subscribe'/> to some remote entity bounces.
The bare jid gets a <presence type='error'/>, but does associate this
with the subscribe.
Besides which, S2S has long been seen as the deployment path - a server
doing XEP-0198 on both S2S and C2S can at least self-interop from the
outset with S2S.
0198 is not usable on s2s unless you're using sasl, because it does
not get offered before the initiator has been authenticated?
philipp
