[Standards-JIG] message events in MUC
jconley at winfessor.com
Wed Jun 30 21:58:11 UTC 2004
I agree that we should not forbid the action in the specification.
However, in large public chats (Like many IRC rooms with hundreds of
users), it would increase the MUC bandwidth and processing overhead
I'm fine with verbiage like: "A client SHOULD NOT send JEP-0020 or
JEP-0085 notifications and a service implementation MAY block these
stanzas to conserve bandwidth." I could see this as an option in the
configuration form of a room.
From: Tijl Houtbeckers [mailto:thoutbeckers at splendo.com]
Sent: Wednesday, June 30, 2004 2:51 PM
To: Jabber protocol discussion list
Subject: Re: [Standards-JIG] message events in MUC
On Wed, 30 Jun 2004 09:38:07 -0600, Peter Saint-Andre
<stpeter at jabber.org>
> Fixing something else in JEP-0045 just now, I noticed that the
> rules prohibit a client from sending JEP-0020 message events (no
> of JEP-0085 chat state notifications) through a groupchat room. Do
> think this is right? Loosening this seems fine with me.
> This raises the issue of JEP-0020 vs. JEP-0085, but that's a can of
> we might not want to open right now...
I think it could be very usefull to see who is typing and who is not in
groupchat. That way you can wait with your reply is you see someone is
still typing (I'd say it could be even more usefull than in 1-on-1 chat
Are there good reasons why JEP-0020 can not be used for this? Could
JEP-0085 handle this more efficiently?
Any blocking of such things because it could cost too much bandwith
very implementation specific to me, not material to put in a spec. using
the word MUST.
Standards-JIG mailing list
Standards-JIG at jabber.org
More information about the Standards