forked from rcaputo/poe
/
README
278 lines (209 loc) · 9.21 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
$Id$
-----------
What POE Is
-----------
POE is an application kernel that uses event driven state machines as
threads. It includes a high-level I/O library that hides most of the
usual client/server tediosity. It has been developed and used in
mission-critical systems since August 1998.
---------------------
Documentation Roadmap
---------------------
The POE manpage's SEE ALSO section lists the topics covered in each
manpage. It's a good starting place.
The CHANGES file lists nearly every change made to POE since 1998,
including ones which have broken backward compatibility. The
backward-breaking changes are marked with exclamation points so they
stand out.
The TODO file includes a roadmap of changes which may break backward
compatibility. Each change includes dates of earliest breakage, which
means you have at least until those dates to update critical programs.
--------------------
Distribution Details
--------------------
This distribution comes with several sample and tutorial programs in
its samples/ directory. These programs are NOT installed because they
have limited use and take up a lot of space.
The lib/ directory includes a few useful utilities, including a basic
test coverage module, harness, and report. The test coverage summary
at the end of this file was generated by that system. These utilities
aren't installed either.
The test programs, in t/, may also be interesting examples, although
they're more geared towards exercising POE. 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 B<that> is
documentation. The generally usable bits of POE are pretty small.
------------------
Basic Installation
------------------
POE may be installed through the CPAN shell in the usual CPAN shell
manner. It typically is:
perl -MCPAN -e 'install POE'
It involves a little more work if you have an older CPAN shell:
perl -MCPAN -e shell
install POE
To install on a Win32 machine using ActiveState's PPM:
ppm install http://poe.sourceforge.net/packages/POE.ppd
--------------------------
Getting The Latest Version
--------------------------
POE can also be installed manually, although Win32 users are
recommended to use the PPM instead. Tarballs are available from at
least three sources:
The most recent stable release can be found at your favorite CPAN
mirror. If you don't have a favorite CPAN mirror, there's always:
ftp://ftp.cpan.org/pub/CPAN/authors/id/R/RC/RCAPUTO/
The most recent development snapshot is available from two locations:
http://poe.perl.org/
http://sourceforge.net/projects/poe/
The SourceForge project includes a CVS repository browser, so you can
look around to see what's new. It also has facilities for people to
submit bug reports, patches, and support requests.
---------------------------
Building The Latest Version
---------------------------
Downloading and unpacking the distribution are left as an exercise for
the reader. See the previous section for tarball locations.
System requirements and copatibility issues are covered in the main
POE manpage. You can preview them before building POE.
perldoc ./POE.pm
Please read the CHANGES and TODO files if you already have programs
which use POE. They contain advance notice of changes which may break
existing code.
less ./CHANGES
less ./TODO
If everything looks good, build POE:
perl Makefile.PL
make
... then test the distribution. This is an important step since it
also ferrets out the modules POE needs. It reports on the POE
components which won't work because of missing dependencies, and it
recommends things to install. Please read the dependency report
carefully.
make test
Now you're ready to install POE, but first you may want to look at its
samples. Some of the samples may be stale: they might not work with
the most recent distribution, but everything is okay as long as "make
test" has passed.
All the programs in the samples subdirectory are written to run from
the distribution directory without POE being installed yet.
cd ./samples
ls -l
[try some]
cd ..
Finally you can install it:
make install
------------
Test Results
------------
Thanks to a-mused and dynweb for their testing time. Someday
SourceForge will get its compile farm together again, and I'll be able
to add six more test systems to this list.
The wallclock seconds are constrained mainly by delays within the
tests themselves. For a more accurate determination of POE's speed,
balance the CPU seconds against the test machine's hardware and
operating system.
** POE 0.1501 on FreeBSD (dngor)
Hardware: Athlon-1000; 512MB RAM
System : FreeBSD 4.3-STABLE
Perl : 5.6.1
Gtk : 0.7005
Tk : 800.022
Event : 0.81
IO::Pty : 0.01
All tests successful.
Files=26, Tests=559, 84 wallclock secs ( 7.65 cusr + 0.78 csys = 8.43 CPU)
** POE 0.15 on Solaris 8 (dynweb)
Hardware: Ultra-80; 2x UltraSparc II-450; 1GB RAM
System : SunOS 5.8
Perl : 5.6.1
Gtk : (not installed)
Tk : 800.023
Event : 0.81
IO::Pty : 0.01
All tests successful, 2 tests skipped.
Files=26, Tests=477, 75 wallclock secs (13.09 cusr + 1.28 csys = 14.37 CPU)
** POE 0.15 on Windows 4.10.2222
Hardware: (unknown)
System : Windows 98 2nd Edition
Perl : v5.6.1, MSWin32-x86-multi-thread, ActiveState build 628
Gtk : (not installed)
Tk : (not installed)
Event : (not installed)
IO::Pty : (not installed)
t\01_sessions.t 14 3584 29 29 100.00% 1-29
t\04_selects.t 2 512 ?? ?? % ??
t\08_errors.t 2 512 26 7 26.92% 20-26
t\14_wheels_ft.t 255 65280 9 9 100.00% 1-9
t\19_filterchange.t 2 512 ?? ?? % ??
t\22_wheel_run.t 2 512 ?? ?? % ??
7 tests skipped.
Failed 6/26 test scripts, 76.92% okay. 45/297 subtests failed, 84.85% okay.
[NB: Several of these test failures have been addressed, if not
fixed.]
** POE 0.1401 on Linux (titanic)
Hardware: dual Celeron 500; 265MB RAM
System : Linux 2.2.15 SMP
Perl : v5.6.0
Gtk : (not installed)
Tk : (not installed)
Event : 0.79
IO::Pty : 0.01
All tests successful, 2 tests skipped.
Files=26, Tests=459, 81 wallclock secs (17.16 cusr + 0.96 csys = 18.12 CPU)
** POE 0.1203 on Linux (a-mused)
Hardware: Celeron 600; unknown RAM
System : Linux 2.4.0-test12
Perl : 5.005_03
Gtk : (unknown)
Tk : (not installed)
Event : (installed; unknown version)
All tests successful, 2 tests skipped.
Files=23, Tests=415, 98 wallclock secs (14.22 cusr + 0.63 csys = 14.85 CPU)
-------------
Test Coverage
-------------
While the test coverage numbers are statistically meaningless, they
still present a fun challenge and some measure of assurance that the
authors care about POE's quality. Here's your grain of salt. Lime
and tequila will be provided upon request. :)
The "Ran" and "Total" numbers are breakpoints that perl's debugger can
step through. The "Covered" number is the percentage of breakpoints
that were actually stepped through during testing.
These results are for version 0.15.
Source File = Ran / Total = Covered
POE.pm = 23 / 24 = 95.83%
POE/Component.pm = 5 / 5 = 100.00%
POE/Component/Server/TCP.pm = 32 / 32 = 100.00%
POE/Driver.pm = 5 / 5 = 100.00%
POE/Driver/SysRW.pm = 45 / 54 = 83.33%
POE/Filter.pm = 5 / 5 = 100.00%
POE/Filter/Block.pm = 51 / 51 = 100.00%
POE/Filter/Grep.pm = 23 / 31 = 74.19%
POE/Filter/HTTPD.pm = 18 / 90 = 20.00%
POE/Filter/Line.pm = 86 / 114 = 75.44%
POE/Filter/Map.pm = 22 / 29 = 75.86%
POE/Filter/RecordBlock.pm = 24 / 48 = 50.00%
POE/Filter/Reference.pm = 81 / 84 = 96.43%
POE/Filter/Stackable.pm = 31 / 40 = 77.50%
POE/Filter/Stream.pm = 21 / 21 = 100.00%
POE/Kernel.pm = 869 / 1120 = 77.59%
POE/Kernel/Event.pm = 1 / 9 = 11.11%
POE/Kernel/Gtk.pm = 2 / 17 = 11.76%
POE/Kernel/Select.pm = 6 / 12 = 50.00%
POE/Kernel/Tk.pm = 2 / 19 = 10.53%
POE/NFA.pm = 114 / 203 = 56.16%
POE/Pipe/OneWay.pm = 21 / 39 = 53.85%
POE/Pipe/TwoWay.pm = 23 / 42 = 54.76%
POE/Preprocessor.pm = 108 / 186 = 58.06%
POE/Session.pm = 177 / 227 = 77.97%
POE/Wheel.pm = 11 / 11 = 100.00%
POE/Wheel/FollowTail.pm = 90 / 108 = 83.33%
POE/Wheel/ListenAccept.pm = 51 / 65 = 78.46%
POE/Wheel/ReadWrite.pm = 135 / 222 = 60.81%
POE/Wheel/Run.pm = 176 / 247 = 71.26%
POE/Wheel/SocketFactory.pm = 205 / 249 = 82.33%
All Told = 2463 / 3409 = 72.25%
Thanks for reading!
-- Rocco Caputo / troc@netrus.net / poe.perl.org / poe.sourceforge.net