I guess we would prefer a separate mechanism for logging info since the
debug callback does imply debug info and probably shouldn't be used in
production code. I think the problem with the headers callback was it wasn't
getting called for data that gets sent out (ftp commands sent to the
server).

-george

on 7/28/03 4:24 PM, Daniel Stenberg at daniel_at_haxx.se wrote:

> I understand your concern.
>
> First, I think that in general, when using CURLOPT_DEBUGFUNCTION libcurl
> should be allowed to run slower, as the name of the option kind of implies
> that this is for debugging and for getting internal info you don't otherwise
> get.
>
> In your particular case, won't a callback for the headers do it?
>
> Besides that, I could imagine a system where we set some kind of bitmask for
> the verbose option to signal what we want sent to the debug function. You have
> any existing ideas/thoughts on what you'd like separated?

-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
Received on 2003-07-29