Experience in the use of Response.Flush

flush|response| Experience

Many times we write ASP programs that take a minute or even a few minutes because they do a lot of things. In order for software users to patiently wait for the program to execute, we often want a progress bar to represent the state of the program's execution. Or at least a descriptive text like: "Data Loading", "Saving data", and so on. At this point we will use the Response.Flush (). He will send the data compiled in the buffer to the client first.

But there are many times when we find that even though we use Response.Flush (), we do not send the previous message to the client to display it. What is presented to us is still screen. After repeated tests, I have come to a conclusion (representing personal opinions, which can be arbitrarily cited, but with the consequences). Is that the content of the flush should be at least 256 bytes. That is, only the compilation produces at least 256 bytes of data to send the information to the client and display after the execution of Response.Flush ().