cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@sundn.de>
Subject AW: [C2]: Proposal for intermediate output stream
Date Fri, 06 Jul 2001 06:00:18 GMT
> Donald Ball wrote:
>
> On Thu, 5 Jul 2001, Sergio Carvalho wrote:
>
> > Wouldn't this break streaming? i.e. producing output even when only
> > part of the result has been processed? Streaming buys you some
> > processing time if you have 'heavy' pages, but still want to follow
> > the rule of thumb of producing some feedback in under 3s and the whole
> > page in 7s.
>
> that's why it should be configurable. but when you're producing lots of
> responses in short amounts of time, it makes sense to buffer them and set
> the content length on the response so that the client can continue to use
> the same http session instead of having to open a new one for each
> resource. right? or is it the case that if a resource is cached, the
> content length will be set on all subsequent responses?
>
Yes, it is. For a completly cached response the content length is always
set.

Carsten

> - donald
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message