[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    Re: [jdev] Getting individual roster items
From:       Arne Claassen <arne () getorganyzd ! com>
Date:       2008-11-25 17:10:30
Message-ID: BAB1BF40-FBAF-48B7-98E2-37ED44F4A6EE () getorganyzd ! com
[Download RAW message or body]

Ok, cool. I was afraid that the ejabberd roundrobin meant that the
component instances wouldn't see all traffic. As i said, i need to do
a spike on components.

thanks!
arne

On Nov 25, 2008, at 8:54 AM, Jack Moffitt wrote:

>> Thanks for the info on components. I definitely need to read up a bit
>> more on it. The only snag I see is that right now, I am taking
>> advantage of broadcast and resource affinity behavior of client bots
>> that can be achieved by sending to the jid with or without a resource
>> identifier. With components, it seems requests would get round-
>> robined
>> in ejabberd, which is actually not desirable for the way my bot
>> currently addresses scaling.
>
> Your component will get anything sent to the domain portion, including
> any node and resources used.  So it's easy enough to write your own
> stanza router inside the component if all you need is broadcast to all
> resources of a bare JID.
>
> jack.
> _______________________________________________
> JDev mailing list
> FAQ: http://www.jabber.org/discussion-lists/jdev-faq
> Forum: http://www.jabberforum.org/forumdisplay.php?f 
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe@jabber.org
> _______________________________________________

_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f 
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe@jabber.org
_______________________________________________
[prev in list] [next in list] [prev in thread] [next in thread]