>But I see that's not 100% (or even 50%?) clear in the spec, so I'll >clarify that in the next version.
Great thanks. hw -- Dr. Heiner Wolf bluehands GmbH & Co.mmunication KG http://www.bluehands.de/people/hw +49 (0721) 16108 75 -- Jabber enabled Virtual Presence on the Web: www.lluna.de Open Source Future History: www.galactic-developments.de >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf >Of Peter Saint-Andre >Sent: Wednesday, September 28, 2005 7:55 PM >To: Jabber software development list >Subject: Re: [jdev] MU-Conference returning "Not Found" > > >Heiner Wolf wrote: > >> I was thinking that MUC is backward compatible to GroupChat. >If I send a >> <presence/> without any mentioning of MUC, then I should get a room >> which is not locked until it is configured. >> >> You are right JEP-0045 tells me in "9.1.2 Creating an >Instant Room", for >> an instant room I must send an empty iq-query-x-'jabber:x:data'. But >> this means that a simple <presence/> won't work, because it will lock >> the room. This makes JEP-0045 incompatible to GroupChat. > >Now that I look at it again, the JEP is probably not as clear as it >could be about room creation. The intent is that if you don't include >the muc extension in the initial presence, the service will create the >room for you and not wait for the config (i.e., backwards-compatible >with old-style groupchat), but that if you do include the muc >extension > then the service requires you to go through the >configuration steps. >But I see that's not 100% (or even 50%?) clear in the spec, so I'll >clarify that in the next version. > >Peter > >-- >Peter Saint-Andre >Jabber Software Foundation >http://www.jabber.org/people/stpeter.shtml >
