From mofx71 at gmail.com Mon Aug 17 08:56:49 2009 From: mofx71 at gmail.com (Valentin MARTINET) Date: Mon, 17 Aug 2009 15:56:49 +0200 Subject: [MUC] How to generate a room name? Message-ID: <326836C5-47F3-466C-955A-AD59B68CFC4A@gmail.com> Hello all, My name Valentin Martinet and I'm currently developping for the SIP Communicator software (sip-communicator.org). I'm debugging multi-user-chat for XMPP, and I'd like to know how a room name should be created, when extending a one-to-one chat to a three (ore more) users chat. For example, I've noticed that Spark software from Ignite Real Time uses the nam?e of the user, followed by a generated string (and followed by @muc-service-name.jabber-server.com). Is this the right way? Thanks in advance for your help! Regards, Valentin ------------------------------------------------------------ Valentin MARTINET mofx71 at gmail.com From dave at cridland.net Mon Aug 17 09:02:55 2009 From: dave at cridland.net (Dave Cridland) Date: Mon, 17 Aug 2009 15:02:55 +0100 Subject: [MUC] How to generate a room name? In-Reply-To: <326836C5-47F3-466C-955A-AD59B68CFC4A@gmail.com> References: <326836C5-47F3-466C-955A-AD59B68CFC4A@gmail.com> Message-ID: <28382.1250517775.293444@puncture> On Mon Aug 17 14:56:49 2009, Valentin MARTINET wrote: > I'm debugging multi-user-chat for XMPP, and I'd like to know how a > room name should be created, when extending a > one-to-one chat to a three (ore more) users chat. > > For example, I've noticed that Spark software from Ignite Real Time > uses the nam?e of the user, followed by a generated string > (and followed by @muc-service-name.jabber-server.com). > Is this the right way? The XEP-0045 specification actually includes a method of requesting a unique room name from the server. Personally, I'd go for client-side generation, assuming you can use a sufficiently random name, though, as this will remove a round-trip, but this is really a matter of personal choice. The important thing to do is to ensure that if the room cannot be joined, to generate a new name and try again, and if it can be joined, to ensure that the room is locked (ie, it's just been created) before anything else. Dave. -- Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at dave.cridland.net - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade From mofx71 at gmail.com Mon Aug 17 09:15:19 2009 From: mofx71 at gmail.com (Valentin MARTINET) Date: Mon, 17 Aug 2009 16:15:19 +0200 Subject: [MUC] How to generate a room name? In-Reply-To: <28382.1250517775.293444@puncture> References: <326836C5-47F3-466C-955A-AD59B68CFC4A@gmail.com> <28382.1250517775.293444@puncture> Message-ID: <493C113D-108A-43B6-87A1-D5F78F01640C@gmail.com> Ok, this is very clear! Thanks for the quick response! Regards, Valentin. Le 17 ao?t 09 ? 16:02, Dave Cridland a ?crit : > On Mon Aug 17 14:56:49 2009, Valentin MARTINET wrote: >> I'm debugging multi-user-chat for XMPP, and I'd like to know how a >> room name should be created, when extending a >> one-to-one chat to a three (ore more) users chat. >> For example, I've noticed that Spark software from Ignite Real >> Time uses the nam?e of the user, followed by a generated string >> (and followed by @muc-service-name.jabber-server.com). >> Is this the right way? > > The XEP-0045 specification actually includes a method of requesting > a unique room name from the server. > > Personally, I'd go for client-side generation, assuming you can use > a sufficiently random name, though, as this will remove a round- > trip, but this is really a matter of personal choice. > > The important thing to do is to ensure that if the room cannot be > joined, to generate a new name and try again, and if it can be > joined, to ensure that the room is locked (ie, it's just been > created) before anything else. > > Dave. > -- > Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at dave.cridland.net > - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ > - http://dave.cridland.net/ > Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade ------------------------------------------------------------ Valentin MARTINET mofx71 at gmail.com