Our application embeds SAS generated html String with Java generated header and footer for the application report.
In our report pages, there are "Back" buttons which use history.back() to
call the same process on the server.
Clients can tolerate waiting a long time after pressing the "generate report" button for the report,
but cannot tolerate the "Back" button taking the same time as "generate report" button.
So I wander if the application can cache the SAS returned String or cache the whole report page
Some where only for "Back" button being pressed.
I do not want cache the html String in Session because I do not know how big the page is returned
We are using a product of oracle called WebCache for such purposes. It does comprehensive caching by making cache of parts of web page.
Besides, the very basic idea of end user hitting a browser back button doesn't appeals much. I think there should be a back link/button on web page which should be used by end user. Also, upon this link you can actually do some caching via some logic in code.