Hi Chuck,
that's true. But is there any means to avoid the problem while working
with a WODisplayGroup ? It uses a EODatabaseDataSource which in turn
seems to always use the session's EOEditingContext by default.
Thanks in advance
Richard
Are you using an editing context from session in the Long Response
page? Stay away from that, especially session.defaultEditingContext or
you will block request dispatch.
Chuck
On May 24, 2004, at 12:32 AM, email@hidden wrote:
Hi all,
WOLongResponse seems to work only for calculation or time consuming
tasks (like prime calculation as Apple example) but when I'm
processing EO objects and saving changes, the page is no more
refreshed.
A workaround is to increased the receive timeout (default value is 30
secondes) for each instance application but it means there is no
progress indicator, and the user is not really aware of which
operation is in progress.
Any suggestions or comments about how to deal with a long processing
(about 60 secondes) with EO objects, including saving, and displaying
progress messages.
Thanks for your suggestions and comments,
Orlando.
