[
http://issues.apache.org/jira/browse/DIREVE-223?page=comments#action_12318624 ]
Stefan Zoerner commented on DIREVE-223:
---------------------------------------
IBM Tivoli Directory Server implements transactions with the help of two
extended operations and an LDAP control.
Extended operations:
1.3.18.0.2.12.5 Begin transaction extended operation
1.3.18.0.2.12.6 End transaction extended operation
Control:
1.3.18.0.2.10.5 Transaction
(to tag operations as part of a transaction)
Details in the online documentation (This is 6.0, but 5.1 and 5.2 support this
as well):
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDS.doc_6.0/progref387.htm
The basic ideas seem to be similar to the grouping of entries described by Kurt
Zeilenga, but it looks to me that the implementation differs from the draft.
The OIDs of the extended operations and the control start with 1.3.18 (IBM).
We have a Tivoli DS installed here but we have never used this feature. I am
not sure whether it is really necessary for a client to be able to group
operations into transactions. But the requirement described by Trustin (all
modifications within the server caused by a single user op are atomic) sounds
interesting.
> Transaction support
> -------------------
>
> Key: DIREVE-223
> URL: http://issues.apache.org/jira/browse/DIREVE-223
> Project: Directory Server
> Type: New Feature
> Versions: 0.8, 0.9, 0.9.1
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Priority: Minor
>
> Currently ApacheDS or any other directory servers don't support transactions.
> It would be really nice if we can add transaction support so that all
> operations including what affected by triggers will be atomic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
