One needs to also note that Jabber.com is run off of their code, I'd
imagine the Jabber commercial server. I have to assume it's that, becouse
I've tested users with hundreds of users in it's 'roster', and had no
problem
But jabber.com's server is advertised as being more scalable than the regular open source version you use!
Also, Todd had written that "Jabberbot's roster on Jabber.com is about 10 times the size of the next
largest user's roster", which leads me to guess that it had thousands, not hundreds, of "from" subscriptions.
I still don't understand why this would be any trouble for the server. All it means is that when the bot logs in or out, the server has to scan its roster and send out <presence> packets to all the subscribers who are currently logged in (and that's probably less than half, I'd guess.) If that brings the server to its knees, wouldn't that imply some kind of design problem?
�Jens
