Hello everyone,
I've been reading the mailing-list archives (especially this thread
http://www.mail-archive.com/[email protected]/msg01908.html ),
and I think the discussed changes would suit my needs pretty well. The
feature I dig most is allowing multiple routers and Session Managers
(SM) on a single domain name to make jabberd2 service more
resilient/easily scalable. I think that works fine with multiple c2s
already (I'll try this in the upcoming days).
- I think the branch made by Alexandre Jousset has not been merged in
the master. Am I right on this ?
- If not, is there any plan to do it, or to implement similar features ?
Also, when having multiple SMs, I guess there's two main ways to do :
- each SM only hosts the data of a subset of the users (if one SM goes
down, some people will have issues).
or
- every user's session data is on every SM (more reliable, more storage
required, and I guess harder to implement to guarantee one user can not
open two session on different SMs at once/would require the admin to set
up replication for the databases of each SM... etc... ).
Both views are valid I guess. I still don't get which approach was most
favoured or was going to be tried.
I'm still not very at ease with jabberd2 code. I've just stared writing
my own "highly customisable" roster module to plug it on
already-existing roster databases. But I'd gladly help with that if needed.
Thanks.
@Alexandre Jousset : if you're still living near Paris, I would gladly
invite you to discuss this around a drink. ^_^. Anyone else in the area ?
--
Sylvain "Gugli" Guglielmi
Gamedev@Nadeo@Ubisoft
