1

If i have the below code: 

<%
out.write("This will print!<br/>");
out.flush();
out.write("This will also print!<br/>");
out.flush(); <-- Should fail.
out.write("This will get sent to the client too!<br/>");
%>

Why is the second flush being allowed?
I thought that a flush will commit a response and being sent to the client. Once a response is commited, you can't write and flush anymore. The first flush commited the response and has sent to the client. So i would expect the second flush to fail.

I also read that for an include on the requestDispatcher, one can flush as many times as you want (but not for a requestDispatcher forward). How is that so?

I'm confused on this and i would appreciate any enlightening. Thanks.

yapkm01
  • 3,590
  • 7
  • 37
  • 62

1 Answers1

4

You can do flush many times. A flush called (automatically by container OR manually by code) caused existing data in output buffer sent to client. After first flush, the response is marked committed. We have no chance to write response headers/cookies After response is committed. After each flush, the buffer will be reset for storing data of next content writes. You can do flush manually or container will do flush when the buffer is full or at the end of request.

LHA
  • 9,398
  • 8
  • 46
  • 85
  • If the first flush has committed the response, i assume you cannot write anymore data to the client. Committed response is a done deal, right? See my edit. I expect the second flush to fail. – yapkm01 Dec 30 '13 at 18:24
  • Yes. You can flush again. Comitted means some response data already sent to client (partial sent) so you can't change response status, setting headers, or forward request to other resources. – LHA Dec 30 '13 at 18:27
  • You can write more data and also do an include? – yapkm01 Dec 30 '13 at 18:28
  • Yes. But forward is not allowed as I explained above. – LHA Dec 30 '13 at 18:31