[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
UUID external format
- To: openldap-devel@openldap.org
- Subject: UUID external format
- From: Emmanuel Lecharny <elecharny@apache.org>
- Date: Fri, 14 Aug 2009 18:18:55 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=89j5ZOtTQ5GQoWzU/GTkfM+e0lA8kCHf73psacQKMVI=; b=x+VE1W+1+rGZPj1H23MSFPqO8k4Rm+DgYokQcVjAtesnCCpIdFzbDdXkAuZcSW5yde cl57q7kjf/f4EmBTNkfzt9u7mnI5V3Ntt1J5D8Fe71x29pu2aE2w/fAYXsHn3SSHCyKq 2ETH/LftFIViUvxvr5Vkn4xiQYNu+Tvb3+SJg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=O2PXm6gNZneaAA0glK7c1dYL1ZDRviP6UDzDaC0/8s/d/4AtEs1ed6KHfol922zJAD VE6aio5lj1a1lLm82QZ1QwQa4qu2NjWK7CZBUWdfpn1MvILr32cs/fkyoZt7bNNOtaDE c6mPEtRfgcmMK/J3u/ienTPhcrNA+IvgsL/mk=
- In-reply-to: <41267.93.149.38.235.1250171300.squirrel@www.aero.polimi.it>
- References: <41267.93.149.38.235.1250171300.squirrel@www.aero.polimi.it>
- User-agent: Thunderbird 2.0.0.22 (X11/20090608)
Hi guys,
a short question about the way OpenLDAP (last version) exposes the
entryUUID during replication. UUID is supposed to be binary :
RFC 4530 :
*2.1 UUID Syntax*
A Universally Unique Identifier (UUID) [RFC4122
<http://www.apps.ietf.org/rfc/rfc4122.html>] is a 16-octet (128-
bit) value that identifies an object. The ASN.1 [X.680] type UUID is
defined to represent UUIDs as follows:
UUID ::= OCTET STRING (SIZE(16))
-- constrained to an UUID [RFC4122 <http://www.apps.ietf.org/rfc/rfc4122.html>]
When the UUID is transfered in the Syncrepl cookies, it's as a String,
not as a byte[] (with a format like xxx-yyyy-zzzz, kindof). Is there any
reason not to transfer the UUID as a byte[] ?
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org