Very good idea, but not yet the solution. When I switch to "caching",
ThreadIdentifyingTransformer.class prints both thread-id's directly at the beginning
instead of printing the second one at the end, which was the behaviour with
profile-caching. This seems to be a good sign. However, the output on the screen
starts to appear if the transformation is finished completely.
Even if I remove all transformations having only a generator and a html serializer, it
does not stream. Maybe it is the serializer?
Its configuration is
<map:serializer logger="sitemap.serializer.html" mime-type="text/html"
name="html" pool-grow="4" pool-max="32" pool-min="4"
src="org.apache.cocoon.serialization.HTMLSerializer">
<buffer-size>1024</buffer-size>
The buffer size seems appropriate. The testfile itself is HUGE.
Regards, Hauke Ernst
> -----Urspr�ngliche Nachricht-----
> Von: Bruno Dumon [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 2. September 2003 21:30
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: AW: AW: AW: Incremental Processing in Cocoon 2.1
>
> On Tue, 2003-09-02 at 21:05, Hauke Ernst wrote:
> <snip/>
> > I use profile-caching and I added that node outputBufferSize, but no
> change in behaviour, sorry.
>
> That explains it all.
>
> profile-caching doesn't work streaming, and should only be used for
> testing performance of individual transformers in the pipeline. Never
> ever use that thing on production systems!
>
> --
> Bruno Dumon http://outerthought.org/
> Outerthought - Open Source, Java & XML Competence Support Center
> [EMAIL PROTECTED] [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
