>> 3. additionally make sure the JSP files of your application or that are >> used from the platform do not contain calls to response.flush()! >> >> >Yes, that's something we can validate and figure out, but I've seen this in >too many cases, and not always a flush() was repsonsible. Also it's some >very hard to validate all scripts and occassions (especially if they are >part of the framework you use).
yes, but currently we are quite convinced that if you have some places in the response rendering (e.g. JSP pages) that do a manual flush, there is no chance the prevent the problem you describe, only with hacks like mocked requests to avoid the flush command hits the servlet engine. not sure if we really should go this way. we assume (have not tested it) the proposal you describe will not help if there are still flush() calls in the code. stefan
