[standards-jig] NEW JEP: Multi-User Chat

Ryan Eatmon reatmon at jabber.org
Sat Sep 14 14:21:34 UTC 2002

One good reason is that to setup the conversation to negotiate things 
like nicks is complicated.  And just doing it based off of type='error' 
is a really bad way of doing it.

Another reason is that overloading the presence tag to do more and more 
is also a bad hack.

It would be nicer to have a cleanly designed protocol to do everything 
all contained within one namespace.

Yes, the initial groupchat protocol was nice and simple.  So leverage 
that and use the simple parts in the new protocol, but don't juse hack 
up the existing one.  DW's groupchat protocol was looking to try and 
bring full groupchat capability to Jabber, which is something we greatly 

Peter G. Millard wrote:
> Julian -
> Why use a much more complex/complicated protocol instead of extending a
> simpler one? Almost every jaber client already implements this basic core
> protocol, and it can be extended to fit the needs that most people have been
> asking for that DW's stuff was trying to solve. It seems that we would get
> more traction by using the existing code base. GC 1.0 wasn't that bad... it
> was simple, and thats why almost all clients implement it.
> my $0.02
> pgm
> ----- Original Message -----
> From: "Julian Missig" <julian at jabber.org>
> To: <standards-jig at jabber.org>
> Sent: Friday, September 13, 2002 10:23 PM
> Subject: Re: [standards-jig] NEW JEP: Multi-User Chat
>>For clarification, are you proposing this JEP as describing a way we
>>should continue to do groupchat in the future, or is it merely
>>documenting a way to extend the current group chat 1.0 protocol? If we
>>going to be defining something new, then let's look at David Waite's
>>conference stuff, not group chat 1.0.
>>On Wednesday, Sep 11, 2002, at 10:29 US/Eastern, Peter Saint-Andre
>>>I have started work on a new JEP that documents the existing "groupchat
>>>1.0" protocol and shows how the desired administrative tasks (room
>>>assigning room admins, kick, ban, etc.) can be implemented using the
>>>jabber:x:data namespace. The JEP is here:
>>>Have at it!
>>Standards-JIG mailing list
>>Standards-JIG at jabber.org
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig


Ryan Eatmon
reatmon at jabber.org

More information about the Standards mailing list