cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <vadim.gritse...@verizon.net>
Subject Re: Cocoon running modes (was Re: Error Handling is NOT working)
Date Thu, 12 Sep 2002 12:46:06 GMT
Nicola Ken Barozzi wrote:

>
> Carsten Ziegeler wrote:
>
>> Might be worth investigating into running modes. Hmm.
>
>
> BTW, I'm happy this discussion came to nice indication and real 
> solutions, kudos to all that partecipate :-)
>
>> But comming back to the original problem ;) - We already have an
>> intermediate
>> output stream implemented and noone really complained about it:
>> Its the buffered output stream in the abstract text serializer...the 
>> only
>> problem here is that a) the size of the buffer might be too small
>> and b) the stream is flushed on recycle().
>>
>> So, if we
>> a) Move this buffered output stream handling out of the serializer
>>    into the environment
>
>
> +1 There is where it belongs architecturally IMHO, thanks for pointing 
> this out, I wasn't aware.
>
>> b) Don't flush the stream on recycling a serializer 
>
>
> Even better: prevent flushng alltogether by making a 
> CocoonIntermediateStream that extends the output stream, and that does 
> nothing on flush, and instead uses an Environment-protected method for 
> flushing, so we can play safe.
>
>> c) Add a small logic checking the buffer size for the current response,
>
>
> +1 and make it configurable.
>
>> we have everything we need.
>>
>> This should work and it should also don't have any impact on the
>> performance as 99% of it is already done.
>

+1 and port to 203 when this is stable. It has same issue.

Vadim


> At least we can see how it works.
> Decoupling from the real stream gives us nice advantages it seems.
>
>> I will give this a try today - and we can see if it works.
>
>
> :-)
>
>> But we should of course continue this discussion about the running modes.
>
>
> Running modes is a nice idea that we already had sometime back, and 
> that now fortunately came back.
> Basically with a single param it should be able to switch configurations.
>
> Hence we can switch from a programmer env conf to a production one 
> quite easily.



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


Mime
View raw message