-
Key: RMS11-35
-
Legacy Issue Number: 15023
-
Status: open
-
Source: Object Management Group ( Larry Johnson [X] (Inactive))
-
Summary:
Our current service model often requires numerous operations to accomplish a task which must be completed or else the repository will be inconsistent. The task of setting aside a record, for example, is not a single operational call. Should connection be lost between the client server, or any operation fail, the repository can be left in an inconsistent state. This violates one of RMS original design principles
-
Reported: RMS 1.0b1 — Tue, 2 Feb 2010 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
RMS11 — Explicit or implicit transaction model is needed
- Key: RMS11-35
- OMG Task Force: Records Management Services V1.1 (RMS) RTF