Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 45878 invoked from network); 15 Feb 2011 22:31:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Feb 2011 22:31:02 -0000 Received: (qmail 80954 invoked by uid 500); 15 Feb 2011 22:31:02 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 80812 invoked by uid 500); 15 Feb 2011 22:31:01 -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 80805 invoked by uid 99); 15 Feb 2011 22:31:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Feb 2011 22:31:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of akarasulu@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Feb 2011 22:30:54 +0000 Received: by wwa36 with SMTP id 36so727633wwa.1 for ; Tue, 15 Feb 2011 14:30:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=a5K7Y91c/lTaxk4i31gU/IOrTWAot8fGNKUoS93W+P4=; b=hbwrvkEWBN4dQikK6gRL8U2/B6F4rHeYHgGetDkMsSSVmtUddcAOnItyMAWpRenhdk WSG4cGgtFhbRtvpmF2Kb+SOR2Ko/8TOeynvBIF4sBgqIKvzIIrJ2+ju80ILmvm3Vr5Pv yHh/J79F+nROgw/2m+rJVAcVZw3258ucyS/eI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=dLiePpzp/NTXJYn3DWoo/UMQxKVm6KSQxFgKNsJnFEwBWzPpYKUG4MzSARO0qaaVUm XXsjBLbcfESaNwVqdPRE0nzTDMnkWVGiHl5sFyM3VzUgnScG6qVVutRAIVWGYns0BVWk Dmjay2z6KmhnBILWAh01uDZ8oChfQGkmumljs= MIME-Version: 1.0 Received: by 10.216.48.211 with SMTP id v61mr4853803web.35.1297809033815; Tue, 15 Feb 2011 14:30:33 -0800 (PST) Sender: akarasulu@gmail.com Received: by 10.216.51.15 with HTTP; Tue, 15 Feb 2011 14:30:33 -0800 (PST) In-Reply-To: <4D5A951C.4080604@gmail.com> References: <4D5A951C.4080604@gmail.com> Date: Wed, 16 Feb 2011 00:30:33 +0200 X-Google-Sender-Auth: XPUE6tjwlYe0hbAsXLoo8xnZJLA Message-ID: Subject: Re: Dn class implemented interfaces From: Alex Karasulu To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=001485f779647267ab049c59b657 X-Virus-Checked: Checked by ClamAV on apache.org --001485f779647267ab049c59b657 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 15, 2011 at 5:00 PM, Emmanuel Lecharny wrote: > Hi again, > > going a bit deeper, I'm wondering if the Dn class should implement the > Cloneable and Serializable interfaces? > > Cloneable is probably not needed, as the Dn is immutable, and Serializable > is also useless, as we already have a DnSerializer helper class that handles > the Dn serialization. Note that we have a DnFactory class in the server > which expect the Dn class to be serializable, but this is probably not > needed, as we never serialize the associated cache to disk. > > thoughts ? > > I agree. However maybe there was some reason why it was made serializable for replication needs however this can be handled with the string representation. Regards, Alex --001485f779647267ab049c59b657 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 15, 2011 at 5:00 PM, Emmanuel Le= charny <elechar= ny@gmail.com> wrote:
Hi again,

going a bit deeper, I'm wondering if the Dn class should implement the = Cloneable and Serializable interfaces?

Cloneable is probably not needed, as the Dn is immutable, and Serializable = is also useless, as we already have a DnSerializer helper class that handle= s the Dn serialization. Note that we have a DnFactory class in the server w= hich expect the Dn class to be serializable, but this is probably not neede= d, as we never serialize the associated cache to disk.

thoughts ?


I agree. However maybe there was some rea= son why it was made serializable for replication needs however this can be = handled with the string representation.

Regards,
Alex
--001485f779647267ab049c59b657--