good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
300 sec timer is unnecessary
Im intersting only on 2s timer for request My guess how it should work is: 1) try to GET with timeout 2s (timer set to internal time + 2sec, but internal time has lag 5s) 2) update internal time at ->recv. 3) fire timeout for GET, because internal time now = real time, and timer+2s is now in the past 4) throw error about timeout... But... maybe before check timeout for connection it already has success status for GET and timeout at this situation is dropped away In reply to Re^4: AnyEvent timers by EV
by Anonymous Monk
|
|