On Sun, Oct 5, 2008 at 5:33 AM, Jonathan Schleifer <[EMAIL PROTECTED]> wrote: > Not every client supports XMPP ping and this does a lot of traffic and isn't > acceptable for mobile devices. Thousands might be a bit exagerated, but you > can really see 5 - 10 resources.
Currently, I send a space to any resource I haven't heard from in 120 seconds, and if the write succeeds I reset the time. If the write fails, I kill them. XMPP-CORE approves using whitespace for a ping, so I don't see the need for "XMPP PING" support. Also, the RFC is quite mute on what should be done about conflicting resources. The new draft actually recommends overriding the resource and adding randomness to it instead of replacing the already-connected one by the same name. At the moment, my code just returns conflict/ and closes the stream.
