While generally a good idea,
different operational modes would make more sense when Cocoon 2.1 enters a
stable stage.
If we introduce modes early on, then everything that we add in the
development cycle will have to be tested twice - once in each mode.

Ivelin

----- Original Message -----
From: "Sylvain Wallez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 11, 2002 9:45 AM
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:[EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to