Carsten Ziegeler wrote:
Vadim Gritsenko (JIRA) wrote:
So, my question is why is the buffer right now set to "unlimited"?
Is there any specific caveat for this?
If you are using caching pipeline then complete response will have to be
buffered
in any case. For non caching pipelines, complete response will have
to be buffered if serializer requires content length to be set.
For all other cases...
The only reason for "unlimited" is error handling.
Yes, of course, forgot to mention this.
I think this outputBuffer is not really needed.
I think this is another example of running modes. During development you
might want to have an unlimited buffer while in production (where never
an error occurs :) ) you can disable it.
Why don't we use javax.servlet.ServletResponse.setBufferSize() instead of
rolling our own buffering?
Vadim
