cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <pati_giac...@yahoo.com>
Subject RE: [report] Cocoon Hackaton #1
Date Wed, 19 Jul 2000 07:03:24 GMT

--- "Timm, Sean" <STimm@mailgo.com> wrote:
> Stefano Mazzocchi [mailto:stefano@apache.org] wrote:
> <snip/>
> >Each pipeline component must be aware of the enviornment objects,
> but
> >only the serializer will be given the access to the output stream.
> >
> >The enviornment objects will follow the Servlet API, but, the 
> >
> > response.getOutputStream()
> > response.getWriter()
> >
> >methods will return an
> >
> > IllegalStateException
> >
> >if called from "generators" and "transformers".
> 
> Hmm...I know it's probably bad form to manipulate the output stream
> prior to
> serialization, so perhaps someone can enlighten me as to a better
> way.  :)
> We've got a producer that takes quite some time, so we modified it to
> report
> its status, and we stream out a progress bar for display until the
> producer's work is complete (writing directly to the output stream,
> of
> course.)  This is currently possible in Cocoon 1, but it sounds like
> everyone wants this access stripped in Cocoon 2.  Is this true?  Is
> there
> any reason this "feature" cannot remain available?

In C2 you can write to the SAX stream which goes directly through to
the serializer. Because C1 uses DOMs which are passed along the
pipeline the serialisation cannot start before every component has
finished its work.

Giacomo
> 
> Thanks,
> Sean T.


=====
--
PWR GmbH, Organisation & Entwicklung      Tel:   +41 (0)1 856 2202
Giacomo Pati, CTO/CEO                     Fax:   +41 (0)1 856 2201
Hintereichenstrasse 7                     Mailto:Giacomo.Pati@pwr.ch
CH-8166 Niederweningen                    Web:   http://www.pwr.ch

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail  Free email you can access from anywhere!
http://mail.yahoo.com/

Mime
View raw message