This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In one of the application, the client browser access a JSP which will access the DB to generate more than 300 tables(each table with 10rows) in the response. The problem is that the client page is getting populated with the tables continuously and so the client processor utilization is 100% for some time.
I am thnking that this problem can be solved if we show some intermediate page that shows a progress bar or a gif image until the server response is completely generated in the server side.
Do you have any idea about how this can be done? Or please suggest me how we can rectify this problem?
I think, regardless of when you send it, that much data is going to tie up the user's machine for a while. Do you really need to send that much to one screen? Would it be possible to page this report instead of sending it all down at once?