[CAUSEWAY-248] Perform concurrency checking within the persistor (rather than rely on every viewer/client to do the check)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2.0-incubating
• Fix Version/s: core-1.0.0
• Component/s: Core
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 23/Aug/12 08:09
• Updated: 17/Dec/12 09:29
• Resolved: 23/Aug/12 09:05

Description

Currently it is the responsibility of each viewer to check whether a domain object has been updated prior to completing an edit.

For example, if an object is displayed, the viewer renders the OID (usually in the HTML) and also caches the version of the object somewhere (either in the HTML, or possibly in a http session). If the user then invokes an action, then the viewer resolves the object and checks that the version has not changed.

This ticket is to move this check into the persistor so that, when an object is resolved, the version is also supplied. The persistor then throws a concurrency check if there is a mismatch.

The intention is for the API of the Persistor to remain unchanged, accepting only an Oid to resolve the object, but to use the version details that can now be stored in the Oid (see ISIS-245).