If you use an MVP pattern this should solve your problem. In this pattern RPCs are issued from the Presenter (Activity in GWT). Each time a user changes Place (URL) the current Activity is destroyed and a new one is created by the new Place for the new view. RPC callbacks that point to the old Activity are discarded silently.
More about places and activities in GWT: https://developers.google.com/web-toolkit/doc/latest/DevGuideMvpActivitiesAndPlaces On Friday, November 23, 2012 12:04:13 PM UTC-6, Alexey Panteleev wrote: > > Hello, > > I've been struggling with this issue for a long time, maybe someone could > help me address this finally? > From time to time it happens that a user navigates to one page wich issues > an RPC to our server but then quickly navigates to another page which > issues yet another RPC to the server while the 1st call is still being > processed by the server. In this case I always see some kind of > SQLException on the server side (I guess for the 1st call) and then the > client also receives an unspecified Exception. > > What is the best practice for dealing with these situations? Should I be > canceling the 1st call before allowing the 2nd one? > We use gwt-dispatch, I did not find a cancel method in that framework > yet. Or should I not allow any new calls until the active one has not > finished? > > Do you ever run into this w/ GWT? > > Thanks much, > Alexey > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/dmgib3SJ-x8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
