> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Daniel McBrearty > Sent: Friday, October 27, 2006 6:17 AM > To: $Bill Luebkert > Cc: perl-win32-users@listserv.ActiveState.com > Subject: Re: sharing access to a socket > > thanks Bill. but why is it so inadvisable? I don't get it. > I'd have thought that some app where you want one task to > execute periodically while another responds to user input was > exactly where you should use threads. (I'll look into your > suggestions though.) > > It seems to be some weirdness in dealing with a socket very > differently to other file handles eg STDOUT. Can anyone > explain what's going on underneath this? > > BTW I also posted this to perl monks: > > http://www.perlmonks.org/?node_id=580907 > > thanks
Daniel - you really should take a look at POE (http://poe.perl.org/) for pseudo-multithreaded-applications (actually event-driven single-threaded apps). I've written a lot of different apps using POE (the last one was a combination of a web-server, dav-server and a udp-sender/responder). While it takes some getting used to in the beginning, you'll soon never look back at "use threads;" and friends. Tobias _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
