Welcome to POE::Stage
POE::Stage is an object oriented interface to POE, a popular event driven framework for Perl. It implements some of the common design patterns that have arisen out of several years of POE application development:
- It provides call/return semantics for asynchronous Perl programs.
- Its request-scoped closures automate state tracking between requests and responses.
- POE::Stage is fully object-oriented, including its thin interfaces to POE's asynchronous services.
- It facilitates extremely high levels of abstraction and class composition. It's easy to totally wrap POE in a customary class interface.
- POE::Stage also provides adapters for POE's classes and components. Software written directly to POE is not a lost investment.
POE::Stage needs you. Progress is a sequence of small steps. Even if you only have a few minutes to spare, that's enough time to:
- See a need and define it. Propose a class, or design one. Someone else may finish it by the time you get back to it.
- Write a virtual base class. They contain virtually no code.
- Implement a method, even if it's just a simple accessor.
- Document a method, or correct some pre-existing documentation while you're learning how things work.
- Write a single test case, especially if you think you've found a bug. It doesn't need to be much.
- Fix something so that a single failing test passes.
- Update a wiki page.
Get a commit bit. They're cheap. See the IRC and e-mail links below.
POE::Stage Links
- Browse the source. Check out the examples directory while you're there.
- Subversion repository.
- Browse the documentation online.
- irc.perl.org #poe or the author's page at search.cpan.org for Q&A or if you need a Subversion commit bit.
About the Site
- TracGuide -- Built-in Trac documentation
- Trac FAQ -- Frequently Asked Questions
- TracSupport -- Trac support
For a complete list of local wiki pages, see TitleIndex.
