Auto-created, persistent rooms in MUC

[m.e.page]

Let me start by saying Prosody rocks. I have taken on the task of
setting up a XMPP service for a small tech group and I've looked at a
veritable plethora of other XMPP servers. We all use a desktop and
mobile clients in MUC simultaneously and this has proven to be a deal-
breaker with eJabberd and OpenFire.

Okay, if I'm missing something, flame me but I have looked high and
low and cannot figure out how to setup an auto-created, persistent
room in MUC. OpenFire does this (sorry) but does not play well with
multiple logins with the same JID. Prosody seems to handle this well
but does not persist the room across reboots or service restarts.

[Waqas Hussain]

Rooms are temporary by default, and are deleted when the last participant leaves. A room owner can use the room configuration dialog to make a room persistent.

How you get to the room configuration dialog depends on what client you are using. In Miranda I can Right-click > Room options > Configure..

Ah, and you can join a room on ejabberd/openfire/etc with the same account from multiple clients by using a different resource for each client.

If you still have problems, post more details, or drop by in our chatroom <http://prosody.im/discuss#chatroom>.

--

Waqas Hussain

[m.e.page]

Client designated resources are somewhat iffy and the results vary
depending on the client. We have noticed odd behavior concerning which
clients see any given message with multiple logins in MUC. I've tried
tweaking the priority settings with some success but not much
consistency. On one hand, I see how message routing in this scenario
would be difficult to manage. On the other hand, there's this:
http://xmpp.org/extensions/xep-0045.html#enter-conflict

Am I reading this wrong?

Thanks for your help,
Mark

On 7 Feb, 18:15, Waqas Hussain <waqa...@gmail.com> wrote:

[Waqas Hussain]

On Mon, Feb 8, 2010 at 5:37 AM, m.e.page <m.e....@gmail.com> wrote:

Client designated resources are somewhat iffy and the results vary
depending on the client. We have noticed odd behavior concerning which
clients see any given message with multiple logins in MUC. I've tried
tweaking the priority settings with some success but not much
consistency. On one hand, I see how message routing in this scenario
would be difficult to manage. On the other hand, there's this:
http://xmpp.org/extensions/xep-0045.html#enter-conflict

Am I reading this wrong?

You are not reading it wrong. The other servers don't support multiple room joins with the same nick (multiple sessions per-nick), i.e., they don't support the second paragraph of the section you linked. With those servers, you can join with different resources only if you join with a different nick from each.

--

Waqas Hussain