in reply to Perl cluster on Jabber

I don't fully understand your question. However, in regard to your questions about threads, select, and forks: It all depends on what problem you want to solve, how you want it to scale, and what issues you are more comfortable resolving.
If you want to create a cluster, then select and threads are a bit harder to use because they exist in one process and can't span over multiple machines without some contortions.
However there's an even easier solution (IMHO): POE
There are components for Jabber and IPC (which can help with clusters) already built.

Replies are listed 'Best First'.
Re^2: Perl cluster on Jabber
by perlmonkdr (Beadle) on Dec 09, 2007 at 22:32 UTC

    Thank you, it's hard to explain because I do not understand how to do it well, the topic happens because I need that the "cluster" was validated against the server and every time someone wants to connect to this "cluster/client", the cluster forward his request to other scripts ...

    A chart is rudimentary:

     
                              
|Client 1| <-> |Jabber Server|  <-|1 º Step|->  |Our Cluster| 
                 |                                 |       | 
                 +-|2º Step|---<------------> |Handler 1| |Handler 2|

    *- 1º Step: Client 1 through contact with the server cluster this redirect its request to handle 1 or 2 depending on the load.

    * 2º Step: handlers interact with the server directly so as not to overload the Cluster.

    Well it is more or less the idea.

    For now I am going to see how I can make implement IPC, POE, Proc::Daemon in this context.

    Anyway any extra help is greatly appreciated :-D.

    Thk a lot big help

[reply]

In Section Seekers of Perl Wisdom