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?!
>
> With unbuffered we will always have the problem that after the first generated
> SAX event we cannot really make sure we are able to present an error page to
> the user...
>
> Or did I miss here something? Sorry, I haven't followed the thread very
> closely up to now...
What you propose above is what I *think* Carsten wants to propose, so I
guess we are ok with it conceptually.
From an implementation POV having an infinite buffer for the output and
prohibiting serializers to close the stream is IMHO the easy and
effective solution.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
