Well, I'm not sure I understand how this is "not a libcurl topic" just
because you dont understand my usage of libcurl.

I'd prefer not to come up with an arbitrary timeout mechanism for persistent
connections, and would rather rely on the mechanism that already exists in
FTP servers. If any other users out there have tried to do similar things,
I'd be interested in hearing from them versus "dropping" my initial question

thanks for the help,
-barry

On 2/24/06, Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Fri, 24 Feb 2006, Barry Baker wrote:
>
> > 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.
>
> I guess what I fail to understand is that why don't you need those
> resources
> while the server is keeping the connection alive?
>
> For possible re-use of the handle and connection?
>
> - If so, why not just re-use the handle when you want that and just ignore
> if
> the connection had closed in between or not?
>
> - If not, then you can just ignore the connected state and just close the
> handle unconditionally
>
> Anyway, this is drifting and is actually no longer a libcurl topic. I'll
> drop
> it here and leave you to do however you want! ;-)
>
> --
> Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
>
Received on 2006-02-25