in reply to Re^2: AnyEvent timers by EV
in thread AnyEvent timers by EV
Most probably ->now_update clears the internal 'cache' entirely, so the persistence is swapped away.
There is no *timer* timeout because in the example code the timeout is set to 300 seconds - a long time after every action is over. There are however *connection* timeouts - most probably the server closes connections that are idle for seconds, and you are keeping them idle by sleeping 5 seconds between the calls.
That's what's happening, in sequence:
1) successful GET; try to keep connection alive
2) enter sleep
3) server closes connection
4) get awake and try a GET; failure. Clear connection cache
5) sleep
6) go to 1)
Krambambuli
---
There is no *timer* timeout because in the example code the timeout is set to 300 seconds - a long time after every action is over. There are however *connection* timeouts - most probably the server closes connections that are idle for seconds, and you are keeping them idle by sleeping 5 seconds between the calls.
That's what's happening, in sequence:
1) successful GET; try to keep connection alive
2) enter sleep
3) server closes connection
4) get awake and try a GET; failure. Clear connection cache
5) sleep
6) go to 1)
Krambambuli
---
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^4: AnyEvent timers by EV
by Anonymous Monk on Apr 05, 2015 at 11:30 UTC | |
by bash (Scribe) on Apr 05, 2015 at 12:36 UTC |
In Section
Seekers of Perl Wisdom