ejabberd - Comments for "the ideal design"

> is there a way to funnel

mfoss — Fri, 14 Aug 2009 15:59:09 +0000

> is there a way to funnel all messages originating
> from shore through a single shore-side IP Addess,
> some sort of proxy perhaps?

One idea: install a bot in ship that joins the room in ship and another room in shore. When a participant of one room says something, the bot 'says' that message on the other room, and viceversa.

Might still suit my needs

webbpinner — Wed, 12 Aug 2009 18:11:20 +0000

Thanks for the explanation. Rather than having "persistent MUCs replicated on both servers" is there a way to funnel all messages originating from shore through a single shore-side IP Addess, some sort of proxy perhaps?

It comes down to security policies, if I can have all messages destined for ejabberd-ship originate from the same shore-based IP address it is much easier for me to get securities approval and makes it much easier to add additional users.

Thanks again,
- Webb

Bad news. All your

mfoss — Fri, 07 Aug 2009 16:58:58 +0000

Bad news. All your description seemed possible with current ejabberd until you reached this sentence:

> I need to have the persistent MUC(s) replicated on both servers

In ejabberd you can replicate persistent information (accounts, contact lists, offline messages, ...) over several nodes of a cluster.

But it cannot replicate user sessions or rooms, because those are live processes, not information. A user session connected to ejabberd-ship is connected to ejabberd-ship. A room that was created in the MUC service at ejabberd-ship lives in that MUC service.

Summary: in ejabbberd it is possible to replicate information, but not possible to 'clone' processes.