Ok Daniel I've got your point.
So is there any active pycurl maintainers reading this mail list?

Another simple question: does libcurl stores some kind of time
internally to calculate timeouts?
In other words when i call setopt(pycurl.TIMEOUT, 5) a time diff will
be calculated with now or with some stored value?
The reason i am asking is because it is seems all owrking ok with
multi.socket_action(pycurl.SOCKET_TIMEOUT, 0) when i do not set
timeouts ( setopt(pycurl.TIMEOUT, 5) and setopt(pycurl.CONNECTTIMEOUT,
1) )

2012/4/29 Daniel Stenberg <daniel_at_haxx.se>:
> On Sun, 29 Apr 2012, Evgeny Turnaev wrote:
>
>>  I as wrote earlier i am going to use socket_all() and the thing that
>> bothers me - is socket_all() going to be removed in near future?
>
>
> In the _near_ future, no. In _a_ future: yes.
>
>
>>  Another option for me would be - to set some high timeouts that i know is
>> not going to be reached (i will remove handle earlier). But the thing that
>> bothers me in this solution is an issue from previous letter: after 130
>> seconds of idle i added fresh new handle to multi and info_read said that it
>> is timed out. Could you please explain me this behavior - is it an error in
>> my code?
>
>
> I don't understand. I would need a more detailed description and please note
> that I am not a pycurl user or hacker. I have enough work with libcurl
> itself!
>
>
> --
>
>  / daniel.haxx.se
> _______________________________________________
> http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-python

-- 
--------------------------------------------
Турнаев Евгений Викторович
+7 906 875 09 43
--------------------------------------------
_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-python