On Wed, 22 Jan 2003, Ufuk Kayserilioglu wrote:

> I am not very familiar with what the DEBUGFUNCTION supplies because I never
> had to use it. However, if it is the same info output by the verbose mode
> then maybe it is too much over head if you want just to be *informed* of
> the URLs that are visited. I was thinking more along the lines of a
> curl_easy_getinfo() option which returns a linked list of visited URLs. The
> way I see it this information could very well be retrieved after the fetch
> rather than during it.

Ah, that might indeed be a fine way to do it too.

> For me both ways are OK and not much problem to implement on my app side.
> However, I guess the DEBUGFUNCTION way would be easier to code inside
> libcurl.

It would! But then again, I guess we should do things the way that causes the
least effort for the libcurl programmers. We should concentrate on getting a
useful and friendly API for the libcurl-users.

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com