On 4/17/07, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Tue, 17 Apr 2007, Robert Iakobashvili wrote:
>
> (Replying only to a part of the previous message - for now)

> I don't see the need for that patch/CURLINFO_ERROR. It simply makes the output
> that would otherwise be stored in the CURLOPT_ERRORBUFFER get sent to the
> debug callback instead and there you filter out only that. I would rather
> recommend you using CURLOPT_ERRORBUFFER instead, as it would then also reduce
> the amount of *printf()s etc within libcurl.

Thank you for your advise. Indeed, this is a valid option.

Still, we need libcurl verbose debugging option at least
for the detailed statistics and counters, that we are generating,
and even more fore future.

To the best of my knowledge CURLOPT_ERRORBUFFER requires
a buffer per CURL-handle of size 256 bytes. Planning dealing with
tens and hundreds thousand of virtual clients - this is the memory
worth to save.

-- 
Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...................................................................
Navigare necesse est, vivere non est necesse
...................................................................
http://curl-loader.sourceforge.net
An open-source HTTP/S, FTP/S traffic
generating, and web testing tool.