Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 3396 invoked from network); 9 Jan 2009 21:55:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jan 2009 21:55:58 -0000 Received: (qmail 83262 invoked by uid 500); 9 Jan 2009 21:55:57 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 83217 invoked by uid 500); 9 Jan 2009 21:55: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 83208 invoked by uid 99); 9 Jan 2009 21:55:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jan 2009 13:55:57 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates 72.14.220.153 as permitted sender) Received: from [72.14.220.153] (HELO fg-out-1718.google.com) (72.14.220.153) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jan 2009 21:55:45 +0000 Received: by fg-out-1718.google.com with SMTP id 13so4655186fge.3 for ; Fri, 09 Jan 2009 13:55:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:user-agent :mime-version:to:subject:content-type:content-transfer-encoding:from; bh=S9FhemtYYdeAuRfh+J2d4Xk0MAsg6VtyT5S8TA0E2/c=; b=Xw/ZA4m3EdMS8SPbZdjTIxuckyxANR5+Nyqw/nTn6p3UZgAa1XQiCxi3rMV5Chxerj ZKeVBj7qc3+hu/sM8tPdRJU29DjSl2QWcqegJSDx4TCwwjwOP6TckkMGlHTV3Ji3+6Vs syivmzSxuCrQbYTFK1sxGhagQXezt61c/TeDY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:subject:content-type :content-transfer-encoding:from; b=NxnSlI2x/I93ea4k2+VsFPGQY9RMosxzMseq5qLCpGB8COBoGZZG9JqKeg+UI9n1Mf N0BknWv+3EJMCj7SORkIygUBhE8XuHRcbIUpiO0feL9cGiOMez4A6Yghk57P/P3sd9rC BDo29yuhiKtZ4jdKph6UcyunwlZztx91px1Ls= Received: by 10.86.94.11 with SMTP id r11mr15088761fgb.53.1231538124782; Fri, 09 Jan 2009 13:55:24 -0800 (PST) Received: from ?192.168.0.11? (vol75-3-82-66-216-176.fbx.proxad.net [82.66.216.176]) by mx.google.com with ESMTPS id e11sm5232949fga.12.2009.01.09.13.55.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 09 Jan 2009 13:55:23 -0800 (PST) Message-ID: <4967C7CA.7050207@nextury.com> Date: Fri, 09 Jan 2009 22:55:22 +0100 User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Apache Directory Developers List Subject: CSN, ADS and OpenLDAP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit From: Emmanuel Lecharny X-Virus-Checked: Checked by ClamAV on apache.org Hi, currently, for replication, we are using a CSN built from http://tools.ietf.org/html/draft-sermersheim-ldap-csn-02 (more or less). In fact, our CSN is a composition of a timestamp (System.currentMillis()), an operation operationSequence and a replicaId. It is constructed this way : timestamp:replicaId:operationSequence (no padding) It's not what OpenLDAP is using. OpenLDAP is based on http://tools.ietf.org/html/draft-ietf-ldup-model-09, and a CSN is constructed this way : " ... * The format of a CSN string is: yyyymmddhhmmssz#s#r#c * where s is a counter of operations within a timeslice, r is * the replica id (normally zero), and c is a counter of * modifications within this operation. s, r, and c are * represented in hex and zero padded to lengths of 6, 3, and * 6, respectively. (In previous implementations r was only 2 digits.) ... " So far, both CSN are incompatible. We could write translators, but I also think that it would be great to avoid having a different structure. Does it makes sense to you ? -- -- cordialement, regards, Emmanuel L�charny www.iktek.com directory.apache.org