> 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? Joe --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
