Hi,

I need the most blazing fast http get possible, for a
multi-threaded app running on multiprocessor
machine...basically it's proxying to an internal
appliance.

Responses are typically only about 8k. Except for
body, content-type and status, everything else in
response is pretty much a don't care.

The appliance that doesn't support any kind of
persistent connections and closes the connection after
each response.

My question is, do any of the lib curl api calls take
advantage of any multi-threading during a simple get,
to speed things up? Or is that too linear a process,
and there's really no multi-threading it can do, one
thing has to happen after the other.

thank you!! :)

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Received on 2006-10-05