On Wed, 15 Feb 2012, Rich Gray wrote:

> This capability would have to be usable from within a write callback
> function to allow the application to do things like cause libcurl to place
> successive returns in contiguous memory. (I don't believe I've seen
> anything about calling libcurl functions from within a callback.)

A zero-copy API could for example also introduce a new write callback which
could allow separate special magic to inform libcurl about the next
buffer/size...

I'm open to allow the first person who wants to write the code to have a say
in how the API would work. Talking is easy. Writing the code is less so.

> 2) Allow the caller to tell libcurl it has not processed all of the callback
> data.

That's indeed a good idea and IMHO, a more interesting one. (This said, I
don't find it interesting enough to actually run ahead and work on it on my
own.)

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