[Standards-JIG] Dead participants in MU-conf, JEP-0045

JD Conley jconley at winfessor.com
Thu Dec 9 18:17:37 UTC 2004

This should work itself out if the MUC service simply tracks presence,
message, and IQ errors.  If a service-unavailable (or other fatal error)
is returned from a resource the MUC service should remove that resource
from any rooms which they are occupying.

If a statement like this isn't buried somewhere in JEP-0045 it really
should be.


> -----Original Message-----
> From: Heiner Wolf [mailto:wolf at bluehands.de]
> Sent: Thursday, December 09, 2004 6:47 AM
> To: mu-conference at jabberstudio.org
> Cc: standards-jig at jabber.org
> Subject: [Standards-JIG] Dead participants in MU-conf, JEP-0045
> Hi,
> I got many dead participants in rooms. Many Clients do not leave
> explicitely and some servers do not detect that clients simply cut the
> connection. Some servers even have s2s problems and can not tell that
> client is offline.
> The room mus be able to determine if clients are still online. It
> check the client from time to time. Is it possible to configure
> that it checks if a client is still alive?
> I propose to add a SHOULD to JEP-0045: The room SHOULD check the
> state by sending jabber:iq:version in 10 minute intervals and it
> remove the client if it does not respond within 1 minute.
> What do you think?
> hw
> --
> Dr. Klaus H. Wolf
> bluehands GmbH & Co.mmunication KG
> http://www.bluehands.de/people/hw
> +49 (0721) 16108 75
> --
> Jabber enabled Virtual Presence on the Web: http://www.lluna.de/
> Open Source Future History: http://www.galactic-developments.com/
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mail.jabber.org/mailman/listinfo/standards-jig

More information about the Standards mailing list