Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 5142 invoked from network); 15 Sep 2005 17:02:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Sep 2005 17:02:29 -0000 Received: (qmail 18172 invoked by uid 500); 15 Sep 2005 17:02:29 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 18131 invoked by uid 500); 15 Sep 2005 17:02:28 -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 18118 invoked by uid 99); 15 Sep 2005 17:02:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Sep 2005 10:02:28 -0700 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=HTML_30_40,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS,URIBL_SBL X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.162.204 as permitted sender) Received: from [64.233.162.204] (HELO zproxy.gmail.com) (64.233.162.204) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Sep 2005 10:02:38 -0700 Received: by zproxy.gmail.com with SMTP id q3so256550nzb for ; Thu, 15 Sep 2005 10:02:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=ec2X43hSRP55nf5zgLUDOWFlKqy1nnljmg+hlghPClXw9thHAq6dQCqhY8yKWbbrWf0x7EzYGE810597jzRCVYUrCQci7opdXui1FLCO/r4caKSk5cm/8yttu+8OVg/v5K1m0NLG6VUotjQU9e1D6DsART4BZ//B4hCBNAWPsSs= Received: by 10.54.143.15 with SMTP id q15mr381528wrd; Thu, 15 Sep 2005 10:02:25 -0700 (PDT) Received: by 10.54.71.11 with HTTP; Thu, 15 Sep 2005 10:02:25 -0700 (PDT) Message-ID: <768dcb2e050915100221fbf9c3@mail.gmail.com> Date: Fri, 16 Sep 2005 02:02:25 +0900 From: Trustin Lee Reply-To: trustin@gmail.com To: Apache Directory Developers List Subject: Re: Discussion on porting X.500 ACIItem to LDAP In-Reply-To: <43299906.3020804@bellsouth.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_18983_5646927.1126803745946" References: <1676.81.215.30.1.1126715701.squirrel@www.cs.hacettepe.edu.tr> <768dcb2e050914171918779fd9@mail.gmail.com> <1448.81.215.30.1.1126764027.squirrel@www.cs.hacettepe.edu.tr> <1126769380.24854.48.camel@wkslx01.iktek.com> <2345.81.215.30.1.1126770183.squirrel@www.cs.hacettepe.edu.tr> <1126774720.7937.12.camel@portable> <1864.81.215.30.1.1126779940.squirrel@www.cs.hacettepe.edu.tr> <43299906.3020804@bellsouth.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_18983_5646927.1126803745946 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, 2005/9/16, Alex Karasulu : >=20 > >It's a good idea to keep unused bits reserved. Then we'll be compatible > >with X.501 and save space a lot. I liked this. > +1 to use the bit string index in the spec as the index into the bit > string for all these reasons. +1, too. >If Trustin provides me a constructor that takes a String then i'll not > >care if he uses your stuff or his own :-) But we should first be sure if > >we'll use bit-list or bstring form. After Alex and Trustin says final > >thoughts i'll finish it up. > > > Can you elaborate on the differences between bit-list and bstring? How > would these differences manifest themselves in a Java representations of > the grantsAndDenials? I don't understand this, either. Could you give me some example?=20 Trustin --=20 what we call human nature is actually human habit -- http://gleamynode.net/ ------=_Part_18983_5646927.1126803745946 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

2005/9/16, Alex Karasulu <aok123@bellsouth.net>:<= blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 2= 04, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> >It's a good idea to keep unused bits reserved. Then we'll be compatible=
>with X.501 and save space a lot. I liked this.
+1 to use the bit= string index in the spec as the index into the bit
string for all these= reasons.

+1, too.

>If Trustin provides me a constructor that ta= kes a String then i'll not
>care if he uses your stuff or his own :-) But we should first be su= re if
>we'll use bit-list or bstring form. After Alex and Trustin say= s final
>thoughts i'll finish it up.
>
Can you elaborate on = the differences between bit-list and bstring?  How
would these differences manifest themselves in a Java representations o= f
the grantsAndDenials?

I don't understand this, ei= ther.  Could you give me some example?

Trustin
= --=20
what we call human nature is actually human habit
--
http://gleamynode.net/ ------=_Part_18983_5646927.1126803745946--