Berin Loritsch wrote:
>
> Gerhard Froehlich wrote:
>
> > Hi,
> > *DISCLAIMER* I'm not that sitemape/pipeline guru.
> >
> > Could you explain, what do you exactly mean with 'chuncked HTTP'?
>
> Chunking refers to witholding the "Content Length" header from the
> HTTP response. When it is easily determinable such as when we are
> reading a file or BLOB from a database, it is preferred to explicitly
> state the Content Length in bytes for the browser. It helps browsers
> and programatic clients determine the expected time for a resource
> download. In SOAP transactions, you need to know the size if possible
> to prevent the server from being overloaded with large attachments.
>
> However, it is common practice to omit the "Content Length" header
> from the response when resources are dynamically created. Even Apache
> HTTPD recommends "Chunking" for dynamic resources. The docs site
> (quite correctly) that it costs more to buffer the the output and determine
> the correct size of the response than it is worth. That is why Apache
> does not buffer the result of a CGI request.
>
> I will say that buffering small chunks of the resource (say 512 bytes at
> a time) does speed up the transmission time due to less time blocking
> in the socket streams.
No, that's not what I meant: buffered output != chunked output.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
