| … | |
… | |
| 59 | to follow. AnyEvent, on the other hand, is lean and to the point by only |
59 | to follow. AnyEvent, on the other hand, is lean and to the point by only |
| 60 | offering the functionality that is useful, in as thin as a wrapper as |
60 | offering the functionality that is useful, in as thin as a wrapper as |
| 61 | technically possible. |
61 | technically possible. |
| 62 | |
62 | |
| 63 | Of course, if you want lots of policy (this can arguably be somewhat |
63 | Of course, if you want lots of policy (this can arguably be somewhat |
| 64 | useful) and you want to force your users to the one and only event model |
64 | useful) and you want to force your users to use the one and only event |
| 65 | your module forces on them, you should I<not> use this module. |
65 | model, you should I<not> use this module. |
| 66 | |
66 | |
| 67 | |
67 | |
| 68 | =head1 DESCRIPTION |
68 | =head1 DESCRIPTION |
| 69 | |
69 | |
| 70 | L<AnyEvent> provides an identical interface to multiple event loops. This |
70 | L<AnyEvent> provides an identical interface to multiple event loops. This |
