| … | |
… | |
| 101 | |
101 | |
| 102 | As long as the returned watcher object is alive, call the C<$callback> |
102 | As long as the returned watcher object is alive, call the C<$callback> |
| 103 | when the events specified in C<$eventmask> happen. Initially, the timeout |
103 | when the events specified in C<$eventmask> happen. Initially, the timeout |
| 104 | is disabled. |
104 | is disabled. |
| 105 | |
105 | |
| 106 | The C<io_ns> variant doesn't add/start the newly created watcher. |
106 | Youc an additionall set a timeout to occur on the watcher, but note that |
|
|
107 | this timeout will not be reset when you get an I/O event in the EV::PERSIST |
|
|
108 | case, and reaching a timeout will always stop the watcher even in the |
|
|
109 | EV::PERSIST case. |
|
|
110 | |
|
|
111 | If you want a timeout to occur only after a specific time of inactivity, set |
|
|
112 | a repeating timeout and do NOT use EV::PERSIST. |
| 107 | |
113 | |
| 108 | Eventmask can be one or more of these constants ORed together: |
114 | Eventmask can be one or more of these constants ORed together: |
| 109 | |
115 | |
| 110 | EV::READ wait until read() wouldn't block anymore |
116 | EV::READ wait until read() wouldn't block anymore |
| 111 | EV::WRITE wait until write() wouldn't block anymore |
117 | EV::WRITE wait until write() wouldn't block anymore |
| 112 | EV::PERSIST stay active after an event occured |
118 | EV::PERSIST stay active after a (non-timeout) event occured |
|
|
119 | |
|
|
120 | The C<io_ns> variant doesn't add/start the newly created watcher. |
| 113 | |
121 | |
| 114 | =item my $w = EV::timer $after, $repeat, $callback |
122 | =item my $w = EV::timer $after, $repeat, $callback |
| 115 | |
123 | |
| 116 | =item my $w = EV::timer_ns $after, $repeat, $callback |
124 | =item my $w = EV::timer_ns $after, $repeat, $callback |
| 117 | |
125 | |
| … | |
… | |
| 138 | |
146 | |
| 139 | This can be used to schedule a callback to run at very regular intervals, |
147 | This can be used to schedule a callback to run at very regular intervals, |
| 140 | as long as the processing time is less then the interval (otherwise |
148 | as long as the processing time is less then the interval (otherwise |
| 141 | obviously events will be skipped). |
149 | obviously events will be skipped). |
| 142 | |
150 | |
|
|
151 | Another way to think about it (for the mathematically inclined) is that |
|
|
152 | C<timer_abs> will try to tun the callback at the next possible time where |
|
|
153 | C<$time = $at (mod $interval)>, regardless of any time jumps. |
|
|
154 | |
| 143 | The C<timer_abs_ns> variant doesn't add/start the newly created watcher. |
155 | The C<timer_abs_ns> variant doesn't add/start the newly created watcher. |
| 144 | |
156 | |
| 145 | =item my $w = EV::signal $signum, $callback |
157 | =item my $w = EV::signal $signum, $callback |
| 146 | |
158 | |
| 147 | =item my $w = EV::signal_ns $signum, $callback |
159 | =item my $w = EV::signal_ns $signum, $callback |
| … | |
… | |
| 209 | =head1 BUGS |
221 | =head1 BUGS |
| 210 | |
222 | |
| 211 | Lots. Libevent itself isn't well tested and rather buggy, and this module |
223 | Lots. Libevent itself isn't well tested and rather buggy, and this module |
| 212 | is quite new at the moment. |
224 | is quite new at the moment. |
| 213 | |
225 | |
| 214 | Please note that the epoll method is not, in general, reliable in |
226 | Please note that the epoll method is not, in general, reliable in programs |
| 215 | programs that use fork (even if no libveent calls are being made in the |
227 | that use fork (even if no libveent calls are being made in the forked |
| 216 | forked process). Since this is such a common issue, this module will |
228 | process). If your program behaves erratically, try setting the environment |
| 217 | force the epoll method in EV to be off *unless* the global variable |
229 | variable C<EVENT_NOEPOLL> first when running the program. |
| 218 | $EV::ENABLE_EPOLL is set to 1 *before* loading this module for the first |
230 | |
| 219 | time. |
231 | In general, if you fork, then you can only use the EV module in one of the |
|
|
232 | children. |
| 220 | |
233 | |
| 221 | =cut |
234 | =cut |
| 222 | |
235 | |
| 223 | our $NPRI = 4; |
236 | our $NPRI = 4; |
| 224 | our $BASE; |
|
|
| 225 | our $ENABLE_EPOLL; |
|
|
| 226 | |
|
|
| 227 | { |
|
|
| 228 | local $ENV{EVENT_NOEPOLL}; |
|
|
| 229 | $ENV{EVENT_NOEPOLL} = 1 unless $ENABLE_EPOLL; |
|
|
| 230 | $BASE = init; |
237 | our $BASE = init; |
| 231 | } |
|
|
| 232 | |
|
|
| 233 | priority_init $NPRI; |
238 | priority_init $NPRI; |
| 234 | |
239 | |
| 235 | push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"]; |
240 | push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"]; |
| 236 | |
241 | |
| 237 | 1; |
242 | 1; |
