| … | |
… | |
| 353 | then this "current" time will differ substantially from the real |
353 | then this "current" time will differ substantially from the real |
| 354 | time, which might affect timers and time-outs. |
354 | time, which might affect timers and time-outs. |
| 355 | |
355 | |
| 356 | When this is the case, you can call this method, which will update |
356 | When this is the case, you can call this method, which will update |
| 357 | the event loop's idea of "current time". |
357 | the event loop's idea of "current time". |
|
|
358 | |
|
|
359 | A typical example would be a script in a web server (e.g. |
|
|
360 | "mod_perl") - when mod_perl executes the script, then the event loop |
|
|
361 | will have the wrong idea about the "current time" (being potentially |
|
|
362 | far in the past, when the script ran the last time). In that case |
|
|
363 | you should arrange a call to "AnyEvent->now_update" each time the |
|
|
364 | web server process wakes up again (e.g. at the start of your script, |
|
|
365 | or in a handler). |
| 358 | |
366 | |
| 359 | Note that updating the time *might* cause some events to be handled. |
367 | Note that updating the time *might* cause some events to be handled. |
| 360 | |
368 | |
| 361 | SIGNAL WATCHERS |
369 | SIGNAL WATCHERS |
| 362 | $w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>); |
370 | $w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>); |
