Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

Race condition between client and server?

Archie Cobbs
9 years ago Apr 18, 2013 8:09pm
Henri Sara
9 years ago Apr 19, 2013 5:39am

On Vaadin 6, there is a log entry on the server about variable changes for a component that does not exist but if I remember correctly this might also cause an out of sync situation in addition to that.

On Vaadin 7 (again if I remember correctly), if the component has been removed before the event is received, there is a log entry (see AbstractCommunicationManager.handleBurst() etc.) but the RPC call or variable change is ignored and the application does not "crash" from the user's point of view.

The removal of a component is the primary issue from the point of view of the framework, handling other race conditions is up to component implementations.

With how most of the standard components are designed, in many cases such extra events should not cause problems and either the server state of the component "wins" on the next update or the update from the client is performed late.

Archie Cobbs
9 years ago Apr 19, 2013 2:24pm