Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 55147 invoked from network); 12 Aug 2005 12:47:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Aug 2005 12:47:59 -0000 Received: (qmail 77155 invoked by uid 500); 12 Aug 2005 12:47:58 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 76955 invoked by uid 500); 12 Aug 2005 12:47:57 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 76937 invoked by uid 99); 12 Aug 2005 12:47:57 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Aug 2005 05:47:55 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 7EF6AEB for ; Fri, 12 Aug 2005 14:47:54 +0200 (CEST) Message-ID: <1634346773.1123850874518.JavaMail.jira@ajax.apache.org> Date: Fri, 12 Aug 2005 14:47:54 +0200 (CEST) From: "Stefan Zoerner (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIREVE-223) Transaction support In-Reply-To: <1191755071.1123833353853.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ 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