Also keep in mind that the user can simply hit the back/forward button of the browser to switch places. In that case it would not really help to disable the view/navigation or using a PopupPanel with active glass panel because the user can still navigate using the browsers buttons. You would have to disable these buttons as well (not quite sure if its possible).
So I would say in some cases its just better to assume that the UI in some rare cases may show wrong data. In your case its maybe not a big deal if a user is shown in a list that is already deleted. If your app user selects this deleted user from the list and you are trying to load it from your database you could tell the app user that its not there and then remove it from the list. So basically you would "repair" the UI state if the app user really requests that deleted user from the list. But it depends on your app if its a good solution or not. If you really have to solve this problem then you probably have to make sure that the server executes the requests from the client in the exact same order as the client sends them. So you might have to implement some sort of a sequence number. Using a sequence number you could reorder the server requests on server side so that they will be executed in the exact same order as they are executed on the client. That way you could make sure that DELETE is always executed before LIST gets executed. -- J. -- 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/-/KXnxz9-HDqkJ. 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.
