The param screen that launches the report is a pure GWT screen. What
I'd like to do is transition our reports so that the server generates
them on the server side (yes I know we have to find a way to scale it)
and then streams the rendered report to the user. This is a data entry
app and reports can be 100s of pages. The user community for this app
is small enough that we can probably handle the temp storage.
On the GWT side I'd like to show a progress bar or "user expectiation
management" type of GUI until the report is ready. I guess the key is
how to make the server-side report generation asynchronous. The
reports are currently generated inside of an EJB session bean.
Maybe some suggestions on clever uses of Incremental Command and Timer
Has anyone else built something like this?
Dave
I simply use a form post to send the parameters, and target the new
window.
but if your problem is the time it takes to generate the report, you
could send the parameters via RPC, then use a timer to send
additional rpcs at particular intervals, updating some UI each time
to let the user know that the report is still being generated. when
the report is finally done, this rpc could return a hash that could
be used with the window.open method to fetch the newly generated
report. this way, it could even take hours (wouldn't that be
horrible) to generate a report and the browser would open it when it
becomes available.
-jason