[jdev] Getting individual roster items

[Arne Claassen]

Jack,

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.

thanks,
arne

On Nov 22, 2008, at 10:06 PM, Jack Moffitt wrote:

>> One of my bot's roster is getting a bit large, so the roster request
>> is quite a chunk. I already persist the roster, so i'd rather just
>> query indivdual roster items on demand to query the subscription
>> state. Is there a modification to the roster IQ to ask for a single
>> jid? Can't find anything like that in the spec.
>
> There is a XEP for this, XEP 237 - Data Sequencing.  It's use with
> rosters is documented here:
> http://xmpp.org/extensions/xep-0237.html#roster
>
> Unfortunately this XEP is experimental and is likely unsupported by  
> servers.
>
> The common solution to this problem is to reimplement your bot as a
> component, and then it can manage its own roster without help from the
> server.
>
> See my post on scalable bots here for more information:
> http://metajack.im/2008/08/04/thoughts-on-scalable-xmpp-bots/
>
> jack.
> _______________________________________________
> JDev mailing list
> FAQ: http://www.jabber.org/discussion-lists/jdev-faq
> Forum: http://www.jabberforum.org/forumdisplay.php?f=20
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________