Home > Archive > PERL POE > January 2006 > About the interesting POE::Stage
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
About the interesting POE::Stage
|
|
| Eriam Schaffter 2006-01-10, 12:24 am |
| Hi POE gurus and authors
I was wondering if POE::Stage is planned to include stage load management
like in SEDA (http://www.eecs.harvard.edu/~mdw/proj/seda/). If I remenber
correctly I saw a reference to SEDA somewhere (on poe.perl.org, on a change
log ?) but I can't remember where (if I remember though it was a reference
written by Rocco).
I wonder also if POE::Stage already have a non blocking IO mechanism ?
Also my understanding is that POE::Stage is about to become the main entry
point to the poe world, is this right ?
If I have understood the concept of stages correctly that would be really
awsome. Is the POE::Stage::* namespace open for modules submissions ?
Thank you all
Eriam Schaffter
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.10/218 - Release Date: 02.01.2006
| |
| Rocco Caputo 2006-01-10, 12:24 am |
| On Jan 2, 2006, at 18:34, Eriam Schaffter wrote:
> Hi POE gurus and authors
>
> I was wondering if POE::Stage is planned to include stage load
> management
> like in SEDA (http://www.eecs.harvard.edu/~mdw/proj/seda/). If I
> remenber
> correctly I saw a reference to SEDA somewhere (on poe.perl.org, on
> a change
> log ?) but I can't remember where (if I remember though it was a
> reference
> written by Rocco).
POE::Stage is still embryonic. There are a lot of vague plans for
it, but development is taking one slow step at a time. Don't expect
high-level, advanced features any time soon.
> I wonder also if POE::Stage already have a non blocking IO mechanism ?
Yes, of a sort. It uses POE for NBIO. High-level I/O is not written
yet. POE::Filter classes will probably be used directly, so we
already have some protocols to work with.
TCP stages are delayed right now. I'm trying to design TCP stages
that can be subclassed to handle their own events, which would be a
LOT simpler than spawning a TCP stage and a separate one to handle
its events. There are some snags to work through, and the design is
a tight maze of inheritance and containership at this point. Some
diagrams may be necessary.
> Also my understanding is that POE::Stage is about to become the
> main entry
> point to the poe world, is this right ?
This is incorrect. "about to become" implies some immediacy, which
is not going to happen with my current schedule.
> If I have understood the concept of stages correctly that would be
> really
> awsome. Is the POE::Stage::* namespace open for modules submissions ?
The namespace can open up as soon as there are naming guidelines.
Please don't use POE::Stage for critical applications just yet. The
API and semantics may need to change as more features are added.
Thanks.
--
Rocco Caputo - rcaputo@pobox.com
|
|
|
|
|