Ticket #1010 (new Defect)

Opened 8 years ago

Last modified 8 years ago

Changing a type definition concurrently

Reported by: jri Owned by: jri
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.8.3
Keywords: Cc: dgf, Malte, JuergeN
Complexity: 8 Area: Robustness
Module: deepamehta-webclient

Description (last modified by jri) (diff)

When 2 users change a type definition concurrently the type definition might get corrupt. This happens because the client-side type caches are not always in-sync due to missing server push.

Assume one user has an old version of a type with 5 child types when it is actually 8 child types meanwhile. If that user adds another child type it is appended to the 5th child type, which now has 2 successors in the sequence. That is the sequences branches at some point, rendering the entire type definition corrupt.

Note: the same can happen when just 1 user is involved but with many Webclient instances opened in several browsers, windows, or tabs.

Change History

comment:1 Changed 8 years ago by jri

  • Description modified (diff)
Note: See TracTickets for help on using tickets.