cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Error Handling is NOT working
Date Wed, 11 Sep 2002 13:36:19 GMT

Sylvain Wallez wrote:
>
> Ivelin Ivanov wrote:
>
> >----- Original Message -----
> >From: "Sylvain Wallez" <sylvain.wallez@anyware-tech.com>
> >To: <cocoon-dev@xml.apache.org>
> >Sent: Wednesday, September 11, 2002 8:01 AM
> >Subject: Re: Error Handling is NOT working
> >
> >
> >>Why does have a serializer to flush its output when it is recycled ?
> >>Flushing (and output stream management) is IMO the responsibility of the
> >>pipeline, and not that of the serializer.
> >>
> >>
> >
> >Agreed. The sitemap interpreter should flush the output stream when it's
> >done interpreting a request.
> >
> >
>
> [Picky mode on]
>
> Nope. Read carefully : "the responsibility of the *pipeline*" ! The
> sitemap responsibility is to build the pipeline by executing the sitemap
> instructions. The interpreter never touches the output stream : it gives
> the Environment object to the pipeline, and this is where the pipeline
> gets the stream.
>

I agree that it's the responsibility of the environment (or servlet) to
flush and close the output stream - but you can't prevent someone from
doing this.

And yes, increasing the buffer size would eliminate an intermediate stream,
if the size is big enough!

We are always talking of "a user friendly Cocoon" and this here is such a
point:
The problem can be solved by a configurable parameter for the buffer size
of the output stream. But this requires knowledge of this parameter and how
to configure it.
A user friendly system should be able to work as expected without changing
configuration parameters.

Carsten


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


Mime
View raw message