> > 2):
> >
> > The browse component doesn't push the newly created room, as I think it should.
> > If I "manually" browse the muc the room shows up as expected, however.
> >
> I'm not sure what you mean by 'pushing'?
The server sends a type='set' browse element, just as when a new user enters
a romm I am already in. See below:
RECV: <iq type='set' to='[EMAIL PROTECTED]/coccinella' from='[EMAIL PROTECTED]'>
<user xmlns='jabber:iq:browse' jid='[EMAIL PROTECTED]/aef751509...'
name='matben'/></iq>
It is reasonable that the MUC component works similarly when I create a room.
After the room is created its browse element is pushed to the client.
There could be complications here. This one is not completely necessary
as the client may browse the room "manually".
Mats
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
