> Currently, the library checks for the added custom header
> "Transfer-Encoding: chunked" and if that is present
> it'll enable the chunked-transfer stuff.
>
> Is this good enough for the library or do we want an easier way to enable
> this? It may be a bit too cryptic and not really something people would just
> guess or something...
>
> Should I just add yet another CURLOPT-option?
Either way would be pretty easy to use, as long as it is clearly documented...

It strikes me that there is already need for a bit more documentation for
which headers CURL will automaticly generate... and that would be a perfectly
fine place to put some doc on how setting some options would control CURL's
request creation too...

Peace. -njg

-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET
comprehensive development tool, built to increase your
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
Received on 2002-12-03