Sterling Hughes wrote:

> Optimally, File I/O should be optimized in two areas -- when cURL
> gets data to write down into a file -- an when cURL reads from
> files for HTTP uploads (the two areas where I believe signifigant
> file I/O is done). There are alot of businesses using libcurl where that
> extra processor cycle *does* matter (at least with PHP there are a few
> that I know of). Yes, premature optimization is the root of all
> evil (or so Knuth says :), but, in this case I think the
> optimizations are worthwhile.

I haven't been following this discussion close, but why don't you
simply provide your own read/write callback functions, which then
uses whatever mechanism that is optimal for you?

_______________________________________________
Curl-library mailing list
http://curl.haxx.se/libcurl/
Received on 2001-08-11