Hi Daniel,
As discussed earlier, we are using socket callbacks for easy handle to
control open fds (connections).
However, we ran into few issues, we suspect possible bug in close callback
implementation in curl.
Below given is the explanation of the issue we found :
To limit the no. of
On Tue, 3 Jan 2012, Mukul Kedare wrote:
(Please don't top-post!)
As suggested, we have tried out callbacks for sockets. We keep socket fd in
our connection pool object along with the curl easy handle, this way we
limit the number of fds with the same connection pool logic of ours.
Following
Hi Daniel,
As suggested, we have tried out callbacks for sockets.
We keep socket fd in our connection pool object along with the curl easy
handle, this way we limit the number of fds with the same connection pool
logic of ours.
Following are our observations :
1. opensocket resolves our problem
Hi Daniel,
It seems like I had not put up the application logic properly in previous
mail. Let me explain the it to you more clearly. Further, let me tell you
what our assumptions were and what we understood after trying out sample
codes and going through curl documentation. :) And finally
Hi,
In our multi threaded application we are maintaining a pool of connections
(pool of easy handles for each URL).
The connection pool has limited set of easy handles per URL.
All the threads, have their own multi handle to which we add the easy
handles from the connection pool based on the
On Wed, 28 Dec 2011, Mukul Kedare wrote:
All the threads, have their own multi handle to which we add the easy
handles from the connection pool based on the URLs to which the requests are
to be made.
Keeping easy handles around for a multi handle will not affect the connection
pool at all.
