On Wed, 31 Mar 2010, Ben Greear wrote:

>> So in what way does it not work with that callback?
>
> At the least, it wasn't flushing data promptly to the screen, but rather was
> buffering it. If you blindly typed in user-name and password and hit enter
> a few times, you could log in..but it wasn't really usable.

I don't understand. How did your version differ then? It used the same
callback, only requiring an extra option first before it did so, or what did I
miss?

> I was also suspicious that comparing function pointers might not work in all
> cases, but that may just be more paranoia (I usually program other than
> 'C').

First, you _can_ compare function pointers just fine, but you could also just
set a variable where CURLOPT_READFUNCTION is set to make it hold the knowledge
if a custom or the internal callback is used. But do we really need that?

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html