Posted By:
erl_grey
Posted On:
Monday, August 26, 2002 08:34 AM
Hi guys, I'm trying to do the following: When a request comes in, do some processing in the server, give back to the user some written indications on the progress, and when finished display the result- all without using http-refresh in the client side. i'm trying very hard not to put any business logic in the jsp, just keep it for display, but it doesn't seem easy with this issue. my current idea of implementation is to receive the request, forward to a jsp, which will contain tags for other resources and will display the progress. yet this implementation has some of the processing logic (and flow) encapsulated in the jsp, and it screams "troubles in the future". if i were using
More>>
Hi guys,
I'm trying to do the following:
When a request comes in, do some processing in the server, give back to the user some written indications on the progress, and when finished display the result- all without using http-refresh in the client side.
i'm trying very hard not to put any business logic in the jsp, just keep it for display, but it doesn't seem easy with this issue.
my current idea of implementation is to receive the request, forward to a jsp, which will contain
tags for other resources and will display the progress. yet this implementation has some of the processing logic (and flow) encapsulated in the jsp, and it screams "troubles in the future".
if i were using straight servlets, i would have probably done it using simple RequestDispatcher.include() calls to status jsp's. anyone has a good design tip ?
Thanks!