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: Cocoon running modes (was Re: Error Handling is NOT working)
Date Thu, 12 Sep 2002 05:53:50 GMT
Might be worth investigating into running modes. Hmm.

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 and
b) Don't flush the stream on recycling a serializer and
c) Add a small logic checking the buffer size for the current response,

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.

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.

Carsten

> -----Original Message-----
> From: Sylvain Wallez [mailto:sylvain.wallez@anyware-tech.com]
> Sent: Wednesday, September 11, 2002 4:46 PM
> To: cocoon-dev@xml.apache.org
> Subject: Cocoon running modes (was Re: Error Handling is NOT working)
>
>
> Torsten Curdt wrote:
>
> ><snip/>
> >
> >Guys, isn't it obvious we cannot realy provide errors in a user friendly
> >manner since we are delivering the page on-the-fly via SAX?
> Buffering the
> >whole page seems to reduce the positve aspects we get from using
> SAX and we
> >get closer to Cocoon1.
> >
> >Maybe we should have two different modes to run cocoon or at
> least pipelines
> >in: buffered and unbuffered. So one could use e.g. buffered for
> development
> >und unbuffered for deployment?!
> >
> >
>
> Is this buffer size only related to development ? I don't think so.
> Error-handlers can also be used in production to handle
> exceptional-but-foreseen conditions (access denied, unavailable
> resource, etc). So the buffer size isn't only a matter of running mode.
>
> However, running mode is a great idea, which could be used for many more
> things than buffer size :
> - central configuration for automatic reload of XSPs and sitemap in dev
> mode (and no reload in production mode),
> - display the Cocoon "blue screen of death" to the browser in dev mode
> and a gentle "system currently unavailable" in production mode,
> - other ideas ?
>
> Sylvain
>
> --
> Sylvain Wallez
>   Anyware Technologies                  Apache Cocoon
>   http://www.anyware-tech.com           mailto:sylvain@apache.org
>
>
>
>
> ---------------------------------------------------------------------
> 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