Hi,
Your code forks off N threads to do HTTP response checking, then waits
for the reply (invokeThreads). Each thread (runHTTPThread) calls
curlGetResponse and *immediately* sends the answer back down the channel
to invokeThreads (checkAuthResponse) -- then waits for half a second
before
Hello, all!
Can somebody please explain, what is the best way of using CURL with several
threads? I wrote simple client, which tries to authenticate against HTTP
server. With running this client, it starts to eat memory insanely (and I know
this code is far, far away of even being close to be
On Wed, Feb 17, 2010 at 07:34:07PM +0200, Eugene Dzhurinsky wrote:
Hopefully, someone could help me in overcoming my ignorance :)
I realized that I can share the same Chan instance over all invocations in
main, and wrap internal function into withCurlDo to ensure only one IO action
gets executed
