POST cgi question - slightly OT

[Dave Cragg]

If Apache is your web server, I think it will automatically return 
"chunked" data if you don't set a "Content-Length" header in your CGI 
script.

Dave

On 20 Oct 2004, at 11:55, jbv wrote:

>
> Andre,
>
> Thanks for the tip (and the link), although I'm not planing
> to use a browser for the POST, but a Rev standalone in the
> following configuration :
> standalone -> Rev-cgi -> DB -> Rev-cgi  -> standalone
>
> But after all, it's still HTTP, and I might consider slicing
> data in small parts if the total amout becomes really huge...
> BTW at which size do data become "huge" ?
>
> Thanks,
> JB
>
>
>
>>
>>
>> One trick to return huge data to the browser is to use a Chunked
>> Transfer-Encoding this way you can send big data by slicing it in 
>> small
>> parts and sending it to the browser in small amounts. The browser will
>> keep accepting the chunked transfer till it ends, it's better than
>> simply piping the whole data. To get a better knowledge of the HTTP
>> protocol refer to this really wonderfull text HTTP Made Really Easy
>> (http://www.jmarshall.com/easy/http/), this text is easy to read and
>> understand, it saved my life while creating revHTTPd.
>>
>> Cheers
>> andre
>>
>> PS: I never coded chunked transfer encodings, if you do so, please
>> share your code!!!! (if I do it first, I'll share mine) =)
>>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>