we have some resources tied up that are associated with our curl handle so
if we dont detect that the server closed down the connection, then those
resources won't be released until the user explicitly closes down the
connection.

On 2/24/06, Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Fri, 24 Feb 2006, Barry Baker wrote:
>
> > I am implementing a layer (command line and API) on top of libcurl that
> > provides for persistent FTP connections and I have a question regarding
> > server timeouts. I had written some code to take and easy handle and
> add it
> > to a multi handle, then use muli_perform, so that I could get at the
> > underlying FTP control socket using curl_multi_fdset. I then used a
> > combination of select() and read() to detect a server timeout of the FTP
> > connection. This worked fine until we started using the SSL support, at
> > which point by doing the combination of the select() and read() we left
> the
> > socket in a bad state, causing curl to just restart a new connection on
> a
> > subsequent command and causing a server timeout to never be detected.
> >
> > Is there an easier way to do this?
>
> Over SSL I seriously doubt you can do this in any simple way, without
> involving some kind of underlying SSL-library (OpenSSL or GnuTLS) magic.
>
> Why do you need to detect the server timeout at all?
>
> --
> Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
>
Received on 2006-02-25