Non-Blocking MySQL Roster

[Ask Bjørn Hansen]

On Feb 1, 2010, at 20:22, Austin Brkich wrote:

> I was wanting to know if anyone knew the limitations of Perl creating
> new threads and such. My idea was to make a sub-routine for Roster &
> Auth that can be run in it's own thread and making 2-5 threads (x2, 1
> set is for Auth, 2nd set is for Roster) and handing over information
> to these new threads.

What Yann described with gearman is the "djabberd way".  Perl has threads, but it's much easier to just use multiple processes and event based programming.

> Which would come back with the information and use the programming already done with DJabberd to reply with the information.
> 
> I know this sounds off but the server I am setting up is going to be
> big, real big (1,000+ Users with people logging in an out). The next
> thing I am going to be adding is caching of information that is going
> to be accessed a lot.


A couple thousand users shouldn't be a big deal unless they all login at the very same second.



 - ask