ASP.NET Long task with no seperate threads
<p>For a long time before asp.net days, when I had a long task I would just have the task run on a page and use some sort of flush to send output to the user. No separate threads or anything. Since asp.net, I've been doing long tasks the same way. I have an aspx page with response.flush to flush output. This seems to be working fine for me (and I have some tasks that run for a couple hours or more) but I keep reading that this is bad but I am wondering why? What are some issues that have happen to you that you wouldn't do this?</p>
