Tree [c8c160] v0_2201 /
History



File Date Author Commit
docs 2000-01-24 Rocco Caputo Rocco Caputo [12d9e3] Document compression mode in Changes
lib 2002-09-03 Rocco Caputo Rocco Caputo [739eca] Fixed an undefined warning in a seldom-used blo...
mylib 2002-09-03 Rocco Caputo Rocco Caputo [c8c160] Rebuild the XML test report if Makefile has cha...
samples 2002-08-30 Rocco Caputo Rocco Caputo [d78f70] Replaced three sample programs with pointers to...
tests 2002-09-01 Rocco Caputo Rocco Caputo [ae4212] sungo spotted a warning in this test. It turns...
HISTORY 1998-11-23 Rocco Caputo Rocco Caputo [bfdcb0] pointless...
MANIFEST 2002-09-03 Rocco Caputo Rocco Caputo [4d4471] Added cvs-log.perl; added the report upload uti...
Makefile.PL 2002-05-17 Matt Cashner Matt Cashner [773db7] drop the spurious warn from the makefile
NEEDS 2002-06-11 Rocco Caputo Rocco Caputo [652851] Peter Chen noticed that the NEEDS file did not ...
README 2002-09-03 Rocco Caputo Rocco Caputo [e44596] Last minute tweaks.
TODO 2001-10-12 Rocco Caputo Rocco Caputo [4a6ece] move unessential information to the web

Read Me

$Id$

--------------------
Detailed Information
--------------------

POE is bigger than this README.  Please see http://poe.perl.org/ for
much more information.

-----------
What POE Is
-----------

POE is a mature framework for creating multitasking programs in Perl.
It has been in active development since 1998.  It has been used in
mission-critical systems such as internetworked financial markets,
file systems, commerce and application servers.

POE is compatible with perl 5.005_03 through 5.6.1 and beyond.

POE includes functions for creating and using components.  Components
are modular, reusable pieces of programs.  Several components have
been published on the CPAN, and more are listed on POE's web site.

POE includes components and libraries for making quick work of network
clients, servers, and peers.  A "hello, world" web application takes
fewer than 50 lines of code, most of which is configuration.

---------------------
Documentation Roadmap
---------------------

POE includes so much documentation that the main man page includes an
index to the others.  See the "SEE ALSO" section in "man POE", or your
system's equivalent.

The CHANGES file lists all the changes in the past year.  A complete
change history, back to August 1998, is available on POE's web site.

--------------------
Distribution Details
--------------------

This distribution includes a samples directory that contains several
well commented example programs.  These programs are NOT installed.
Better examples are being written all the time and are available
online in the POE Cookbook.

POE's test programs may also be interesting examples, but they're more
for exercising POE than illustrating good coding practices.  The tests
also aren't installed, in case you were wondering.

All in all, the actual installed bits of POE are probably around a
third of the total distribution, and about a quarter of POE's
installed footprint is documentation.

--------------
Installing POE
--------------

See http://poe.perl.org/?Where_to_Get_POE for download sites, Windows
tips, and anonymous CVS instructions.

POE may be installed through the CPAN shell in the usual CPAN shell
manner.

  perl -MCPAN -e 'install POE'

It involves a little more work if you have an older CPAN shell:

  perl -MCPAN -e shell
  cpan> install POE

To install on a Win32 machine using ActiveState's PPM:

  ppm install http://poe.sourceforge.net/packages/POE.ppd

POE can also be installed manually, and the latest versions of things
are available in CVS.

------------
Test Results
------------

POE's test results are large and constantly changing, so it makes more
sense that they are on the web.

  http://eekeek.org/poe-tests/
    -- Automated test reports by users like you.

  http://poe.perl.org/?POE%27s_test_results
    -- Manually maintained test reports, also by users like you.

  http://testers.cpan.org/search?request=dist&dist=POE
    -- CPAN testers' reports.

POE's ongoing improvement relies on your feedback.  The easiest way to
do that is included in the POE distribution itself.  The Makefile
includes two targets: 'testreport' and 'reportupload'.

  make testreport
  make reportupload

Running 'make testreport' will run the test suite and generate an XML
file summarizing the test results named 'poe_report.xml'.  If you have
an active non-proxied internet connection, running 'make reportupload'
will transmit your test results to the POE test server.

If 'make reportupload' fails, go to http://eekeek.org/poe-tests/ and
upload the poe_report.xml file using the form on that page.

Uploaded test results can be viewed at http://eekeek.org/poe-tests/.

-------------
Test Coverage
-------------

POE's test coverage report has also moved onto the 'web.  It gives a
very rough idea of the amount of POE that's been at least cursorily
tested, but it should not be used as an accurate gauge of quality.

  http://poe.perl.org/?POE%27s_test_coverage_report

----
Bye!
----

Thanks for reading!

-- Rocco Caputo / rcaputo@cpan.org / poe.perl.org / poe.sourceforge.net