These exceptions on the next request are problematic for us because that means all the data entered into a form and being submitted will be lost when the exception occurs. How are you dealing with these kind of issues?
The app uses aggressive auto saving when editing. Only issue is creating new data (through a wizard or similar) which can be lost. Currently we live with it and try to minimize that possibility by doing updates when the app isn't used that much.
But generally you could (auto)save new data into the browser's local storage until it has been saved on the server. Then you can restore the data in the UI in case the page reloads.
-- J.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment