IMO, you're suggestion to resume a session is really good, so the resource could get a session ID then. But until we have a XEP that does that, I'd like to keep it the way we have it and make it possible to use both - once we can resume sessions, clients that support that could ask for a random resource, while other clients still get a static one.
Plus I see one problem with resuming a session: You don't know what got lost. So we also need wide XEP-0198 implementation. Otherwise we can't resend on resume what got lost.
-- Jonathan
PGP.sig
Description: This is a digitally signed message part
