Weeeelllll the problem is with the after thread exit clean up code inside
the interpreter. If you do not call the $thread-> join to clean up and make
the number of your threads static and not dynamically created you are
fine. Otherwise after a few news and joins things get hairy and the
interpeter crashes


I wrote a multithreaded telnet to odbc server using this approach !!

As for the number of threads that are actually good , it seems to be a
wide ranging magic munber between 2 and 15 dependant on the machine :-(

I just wish fork would work with signals , none of the above would be
necessary



On Fri, 30 Jul 2004, John Deighan wrote:

>  Date: Fri, 30 Jul 2004 09:09:05 -0400
>  From: John Deighan <jdeighan@[...].com>
>  To: perl-win32-users@[...].com
>  Subject: Re: Perl threads crash perl
> 
>  Seeing as noone else has responded to this, let me simply say that I tried
>  to develop an application using Perl threads, and in my opinion, Perl
>  threads are seriously broken. We had to re-write the application without
>  threads.
> 
>  The main problem was that threads would die, but I found no reliable way of
>  detecting this. Also, some advice I found on the web said that you
>  shouldn't create too many threads - they weren't designed for that.
>  However, there was no mention of what the limit might be, how to determine
>  the limit, or how to discover whether thread creation succeeded or failed.
>  All this means that if you want to create a couple of threads, it should
>  (?) work, but beyond that, who knows?
> 

-- 
Angelos Karageorgiou
Masters of Computer Science
City University of New York
http://www.unix.gr

_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs