Please note: this project is inactive since early 2006

6.3.2 Sessioning

The second approach involves a per-session creation mechanism for EditingContexts.

The framework provides the module utilities.EditingContextSessioning for such situations. This module acts as central repository to which a sessioning mechanism can be bound for creating, accessing and destroying an EditingContext as sessions come up and expire. The module documentation gives full details about its methods and how they can be used.

Known problem:

By definition, such a configuration isolates the changes different users make until they are committed. The problem here is that even after a user has committed changes, the other users that are already connected and whose session already got an EditingContext will not see the changes made to objects previously fetched - new users connecting afterwards will see the changes, though, as will current users who did not fetch the updated objects before they were committed.

This is due to a feature missing in the framework, where changes to an EditingContext are not broadcasted to others. Resolution of this issue is planned for after release 0.9.

There is currently no satisfying solution for this problem.

Comments are welcome: Sebastien Bigaret / Modeling Home Page
Hosted Logo