[ejabberd] MUC / JEP-0045

Sergei Golovan sgolovan at nm.ru
Wed Jan 4 21:37:38 MSK 2006


On Wed, Jan 04, 2006 at 07:12:30PM +0100, Le Boulanger Yann wrote:
> Hi all,
> 
> when I read JEP-0045, I see that (section 9.1.1, workflow sequence #2):
> 
> "If this user is allowed to create a room and the room does not yet 
> exist, the service MUST create the room according to some default 
> configuration, assign the requesting user as the initial room owner, and 
> add the owner to the room but not allow anyone else to enter the room 
> (effectively "locking" the room)."
> 
> but when I create a room on an ejabberd server, it is never locked, even 
> if I don't configure it. So users can join it before I configure it. Is 
> it a bug in MUC implementation of ejabberd ? cause it violates the JEP.

Yes. ejabberd never locks the room. And I don't see any reason (except the
word MUST in JEP-0045) why the room has to be locked after its creation.

I think that it's not a good practice to force users doing something. If user
wants to configure room, he/she can do it.

-- 
Sergei 'TeopeTuK' Golovan


More information about the ejabberd mailing list