You're right, i should describe this more as 'switching between processes'
kind of threading... basicly it takes over functionality kernel's normally
do... basicly one should call it a 'timesliced application kernel that
simulates threads'... it defines it's own 'threads' as 'states' between
which it switches...
Altho, on a happy note, there *is* work on ithreads which should go into 5.8
if all goes well... who knows we might get nice and stable and cool and and
and...*hopes* in perl 6...
on a side note, you probably dont want to use fork on NT seeing the way it's
set up... i've found POE to be a *lot* more safe and effective... but that's
just my 2 bits
hope this clears things up
Jos Boumans
----- Original Message -----
From: "Michael Fowler" <[EMAIL PROTECTED]>
To: "Jos I. Boumans" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 8:26 PM
Subject: Re: Pooling of objects and session data
> On Mon, Jun 25, 2001 at 07:59:51PM +0200, Jos I. Boumans wrote:
> > poe-test.pl is the most basic one, simple starting a few threads
>
> You keep mentioning threads with relation to POE. I hope no one is under
> the mistaken impression that POE supports threads as in POSIX threads, or
> seperate threads of execution. POE's threading support is strictly
> timesliced, meaning it can only do one thing at a time, it just does a
> really good job of switching between things to do.
>
> Don't get me wrong, I love POE. I just wish it had true thread support,
but
> that isn't going to be a possibility until Perl's threads stabilize.
> Threads in Perl 5, unfortunately, will probably never stabilize. In the
> meantime, however, we have timeslicing and the sledgehammer of threads,
> fork.
>
>
> Michael
> --
> Administrator www.shoebox.net
> Programmer, System Administrator www.gallanttech.com
> --
>
