Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 209.85.161.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=H3KlTcBRlWYYqWIFPUCQbWClnWXDQDtSAM24l32IM4Ot17c7w8LdoFIwL19S7t0IBv
         5rh+HylqwCSMlQEQ8+vezpBkx0Dkat3FquTPIzkkUyUzxNKUJtDvnVPKTqwpRBSun5Uw
         M1eJgTeYUg1dtjtkA9JJL3GkJ7wiA9+KW9g1g=
Message-ID: <4D5A951C.4080604@gmail.com>
Date: Tue, 15 Feb 2011 16:00:44 +0100
From: Emmanuel Lecharny <elecharny@gmail.com>
Reply-To: elecharny@apache.org
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Dn class implemented interfaces
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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 ?

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com