[jdev] xmpp4r component development

[Adam Pisoni]

Yeah, my specific component represents 1 (or a few) bots which  
themselves may have extremely large rosters.   So writing it as a  
component allows me to control the whole roster/presence process in a  
scaleable, fault-tolerant way.    I'm using ejabberd to back it up.

Though again, the goal is to create a general framework that makes  
component (not necessarily bot) creation easy... or at least  
easier.    It will probably never be as easy as writing a simple  
client using xmpp4r-simple, but at least you won't have to reinvent  
the wheel... as I'm having to do.

Who are the gnip folks and what are they doing that is so relevant?

adam



On Jun 18, 2008, at 5:28 AM, Peter Saint-Andre wrote:

> On 06/18/2008 6:07 AM, Jonathan Dickinson wrote:
>> Hey Adam,
>>
>> A load-balancable bot? I assume that means that your chatbot can  
>> have x amounts of real contacts.
>
> He may mean something like twitter at twitter.com or jaiku at jaiku.com.  
> Often
> people start out writing those as bots but then they find that the bot
> doesn't scale up to 10,000 contacts so they convert it to a component.
> Perhaps the Gnip folks plan to make that transition easier or even
> unnecessary in the first place. Pure speculation. :)
>
> Peter
>
> -- 
> Peter Saint-Andre
> https://stpeter.im/
>
> _______________________________________________
> 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
> _______________________________________________