Is it a bad idea to write a multi-threaded TCP server daemon in Perl?

Question

Is it a good idea to write multi-threaded programs (in particular, TCP server daemons) in Perl?

Answer 1

Perl is a great server language. If you find yourself in any areas where the interpreted code is confusing the application, you can write extension code in C to handle it.

You can also see non-blocking I / O to avoid overhead on threads. IO :: Lambda is a good module for this, simplifying event-based programming to several [anonymous] routines.

Answer 2

Perl, , , . . perldoc threads.

Answer 3

​​ POE, POE::Wheel::Run .

Answer 4

Perl, ithreads. , , C, . . perldoc perlthrtut.

Answer 5

, , . , .

, . , , , .

- POE AnyEvent , . , , , . Windows Linux, .

Answer 6

, , , , , .

, , C/++, / . Perl ( , , ), , C/++.

Answer 7

, . , , : Perl ithreads

:

, , perl 5.005, Perl ithreads. ? , , , . , . , , , , . ! :

use threads ();
my $foo;
threads->new( sub {print "thread: coderef = ".\$foo."\n"} )->join;
print "  main: coderef = ".\$foo."\n";

:

thread: coderef = SCALAR(0x1eefb4)
  main: coderef = SCALAR(0x107c90)

, , . , , . , . ? . ( , ), "". , , "" , , . , - ( Thread:: Tie).