[ejabberd] Components, addressing specific connections
arne at getorganyzd.com
Mon Dec 8 20:05:52 MSK 2008
Is there a place where these balancing options and other arguments are
documented, or do i need to go to source code? I googled around and
wasn't able to track anything down. Regarding your twitter reply on
the same subject (i'm sdether), I know it's not an ejabberd issue, but
just that the spec really doesn't say anything about what the behavior
should be, which is why I hoped that ejabberd's implementation had
different config options to deal with affinity, balancing, etc. and it
sounds like it does, i just haven't figured it out yet.
On Dec 8, 2008, at 2:12 AM, Mickaël Rémond wrote:
> Hello Arne,
> Le 7 déc. 08 à 22:17, Arne Claassen a écrit :
>> I've been doing programming against client connections so far and
>> some of my uses are running into issues with rosters, so i thought
>> i'd re-implement as components, but it seems i loose the benefit of
>> routing to a particular connection and can't even broadcast to all
>> connections. Are there configuration options for ejabberd_service
>> that allow you to defeat round-robin and introduce resource affinity?
>> I.e. if one connecton sends a message to client and the client
>> responds, is there a way to make sure the response actually gets
>> back to the originator not the next connection in the round robin
> You should look into the balancing option. Several algorithms are
> possible that adds stickiness.
> Mickaël Rémond
> ejabberd mailing list
> ejabberd at jabber.ru
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ejabberd