[jdev] Jabberd 2.x high availability

[Mathias Herberts]

Hi there,

I am posting this message as a follow-up to Rob Norris' message on his 
thoughts about High Availability in the jabberd XMPP daemon.

Remy Harel is working in my team for six month with a clear goal, making 
Jabberd 2.x an enterprise class XMPP daemon. Among the tasks he has to 
achieve is adding high availability and scalability to the jabberd 2.x 
architecture. This means mainly removing all SPOFs and ensuring that we 
can both handle the load and tolerate components failures without 
violating the XMPP protocol.

To bounce on Rob's remark, we were planning on implementing a sequencing 
of the packets among a session (between any two JIDs) for all packets 
exchanged between jabberd 2.x components. The c2s would be responsible 
for the initial sequence number assignment and also for the queueing 
strategy to enforce should packets come out of order.

Before we start working hard, are there any other initiatives of this 
kind around jabberd 2.x. If so or even if not, is anybody else 
interested by our work and may be willing to participate?

Any feedback would be appreciated.

Mathias.