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 (herse.apache.org: domain of ole.ersoy@gmail.com designates
 66.249.82.239 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding;
        b=Rqz1praEPgGOJ/VCEeNbB2EnCueyLOBmA3H+1n35YbVsVtpKVRm+3r2aTpXfXIC2+plwGVjsgek0KwqHaV6i8/6GXHU0k+PysXWmUp/b7NjD4fXie/w0Wom8usEZ+1dJMyQ5P/ALqFavm82sZOgohZV15e+7S5BoIHdhQ5bhSC8=
Message-ID: <4628E04D.9020300@gmail.com>
Date: Fri, 20 Apr 2007 10:46:21 -0500
From: Ole Ersoy <ole.ersoy@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070302)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: [Schema] Constants - A happy Medium?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hey Guys,

I know what you are thinking.  Heeeere he goes again :-)

And you would be right.  But I think I may have found
a simpler solution that everyone can live with.

In order to minimize the DAS's dependencies, I created another
set of constants and I'm naming them like this:

AttributeTypeConstants

So AttributeType's constants have their own interface.

This completely eliminates the need for a convention,
and it's clear that these are attribute types.

So to get the CN attribute type we just do:
AttributeTypeConstants.CN

It's short and we see that it is an AttributeType.

So if we wanted to we could keep the
the other constants for now and slowly
introduce these.  That way
we don't break client code, and the
names are shorter still and more precise.

Cheers,
- Ole