On Mar 5, 2010, at 20:22, Bob McConnell wrote: > From: Jay Savage >> On Wed, Mar 3, 2010 at 8:28 AM, Bob McConnell <r...@cbord.com> wrote: >> [snip] >>> >>> However, if the application is this complex, is Perl really the best >>> language to use? It would not be my first choice. >> >> That is a very strange statement to make on a Perl beginners list, not >> least because it's complete bosh.
It is bosh. Perl's socket implementations and vast library make it ideal for this sort of programming domain. >> >> What better language to simple network control structures? This is >> exactly the sort of task that Perl accomplishes better and more easily >> than any other language out there, and why it's "the glue of the >> internet." > In particular, all too often I see warnings that threads > are still not handled very well in Perl. Until that changes, I will not > consider Perl for anything that requires multi-threaded code. I wouldn't use perl threads because I wouldn't use threads. Quoting someone way smarter than me: "Unix processes are one of two techniques for achieving reliable concurrency and parallelism in server applications. Threads are out. You can use processes, or async/events, or both processes and async/events, but definitely not threads. Threads are out."[0] It also appears the OP knows what he is doing and has already some working code, looks like perl made this hard task at least possible. Jeremiah 0. http://tomayko.com/writings/unicorn-is-unix -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
