in reply to Working in parallel

Since Net::Telnet is a IO::Socket subclass, you can use it as the handle to the connection with your server. You can then use an event, select or poll-based interface to wait for data on your multiple connections, f.e. Event, EV, AnyEvent::Handle, POE::Wheel::ReadWrite, IO::Select, IO::Poll, select and poll.

This way you can use one process to collect all your data, avoiding forking, threading or IPC.

Replies are listed 'Best First'.
Re^2: Working in parallel
by locked_user sundialsvc4 (Abbot) on Aug 20, 2010 at 19:41 UTC

    That brings up a very important point:   many server programs need to handle “many, even hundreds, of input channels,” but a simple socket-select design often works beautifully for them, with no need for threads.

    Also, if the design does start getting complicated, a little bell should go off in your head:   “this has probably been done a thousand times before, and it's got to be on CPAN somewhere.”   So, before you go far down the primrose-path of coding something new, you stop writing and start looking.   Works every time.   You can find everything from well-tested component pieces, to battle-hardened complete frameworks.

Re^2: Working in parallel
by Anonymous Monk on Aug 20, 2010 at 14:01 UTC

    Could you post a simple example?

[reply]
[reply]
[d/l]

In Section Seekers of Perl Wisdom