Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
488 views
in Technique[技术] by (71.8m points)

c# - Can we use Response.Flush () instead of Response.End()

Response.End() generates ThreadAbortException.

Using HttpContext.Current.ApplicationInstance.CompleteRequest in place of it doesn't solve the problem.

So, can we use Response.Flush() instead of Response.End()

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

The Response.Flush() is send to the browser what is on buffer, but is not stop the processing of the page, so it will continue the execution of the next steps.

What is Response.End() do is to stop the execution steps on the next function call in the asp.net Page Life Cycle. http://msdn.microsoft.com/en-us/library/ms178472.aspx

And that's why it need to throw an exception, to throw out of the loop of the series of call.

One alternative is the Response.Close() but this also is not stop the execution steps and probably you have some other error if you try to send something after the close of the connection with the browser. if you do Response.Close() you need to also do Flush() just before you call it or else browser gets unpredictable data.

you can also read : Redirect to a page with endResponse to true VS CompleteRequest and security thread


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...