| … | |
… | |
| 362 | this "current" time will differ substantially from the real time, which |
362 | this "current" time will differ substantially from the real time, which |
| 363 | might affect timers and time-outs. |
363 | might affect timers and time-outs. |
| 364 | |
364 | |
| 365 | When this is the case, you can call this method, which will update the |
365 | When this is the case, you can call this method, which will update the |
| 366 | event loop's idea of "current time". |
366 | event loop's idea of "current time". |
|
|
367 | |
|
|
368 | A typical example would be a script in a web server (e.g. C<mod_perl>) - |
|
|
369 | when mod_perl executes the script, then the event loop will have the wrong |
|
|
370 | idea about the "current time" (being potentially far in the past, when the |
|
|
371 | script ran the last time). In that case you should arrange a call to C<< |
|
|
372 | AnyEvent->now_update >> each time the web server process wakes up again |
|
|
373 | (e.g. at the start of your script, or in a handler). |
| 367 | |
374 | |
| 368 | Note that updating the time I<might> cause some events to be handled. |
375 | Note that updating the time I<might> cause some events to be handled. |
| 369 | |
376 | |
| 370 | =back |
377 | =back |
| 371 | |
378 | |
