From: Joe Mason
From: [email protected]
[[email protected]] on
behalf of Ellié Computing Open Source Program
[[email protected]]
this option is a bit of the kind "one to rule them all"... because it
indeed
cover all the cases where the developer knows connection reuse is
unpractical, its name might be generalized to
'CULROPT_REUSE_GENERATION'...
by the way, when the user increments the value for each request it
actually
does the same as FRESH_CONNECT, letting libcurl unused handles.
Could the caller not just keep track of the "reuse generation" and set
FRESH_CONNECT on handles after it changes?
it does not seem possible that way because the "reuse generation" that could
be associated through the private data to the new CURL* needs to be compared
to something in the actual connection and this information is not available
at all in libcurl (as it would be discarded when un-linking the actual
connection from the previous CURL*).
Armel
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
