Jens Reufsteck wrote:
Hi all,
I need to process a large file and used a noncaching-pipeline with
outputBufferSize=0 on Cocoon 2.1.7. Worked fine - apart from multithreading
problems, which made me change to a newer version of Cocoon.
On 2.1.9 outputBufferSize doesn't seem to have any effect. Output is always
buffered to the end. I've also tried setting this on a pipe-level, didn't
help. The only hint I found in the mail archives is a similar post some time
ago - unfortunately without answer. Any hint would be welcome!
I briefly looked at the code of 2.1.9 and it seems that there is a
potential problem. Could you please debug and see how often
org.apache.cocoon.environment.AbstractEnvironment#getOutputStream(int)
is called during the request processing and with which int values?
Second question: I used to use non-caching=true. Now, it seems to be
type=noncaching. Has this changed? Is it still the same mechanism?
Where did you use this "non-caching=true"? Afaik the correct way has
always been type="noncaching" :)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
