Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 7448 invoked from network); 6 Apr 2007 01:12:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Apr 2007 01:12:59 -0000 Received: (qmail 54644 invoked by uid 500); 6 Apr 2007 01:13:05 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 54600 invoked by uid 500); 6 Apr 2007 01:13:05 -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 54587 invoked by uid 99); 6 Apr 2007 01:13:05 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 18:13:05 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 66.249.92.173 as permitted sender) Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 18:12:57 -0700 Received: by ug-out-1314.google.com with SMTP id 71so1142007ugh for ; Thu, 05 Apr 2007 18:12:36 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=XVQM+yjbbUAgtm0hKSmqTLkftly3+3i9ec8iitFUoPuHM5ByEj5WA3VHsAI/go4Lhfwglu/WQaUvbo1O9S0KzUcL+8RcMBc0IlvNpN5XPCQDQnUxSwJYdTz+sxuUgRIqBJFHio3NMgj0jhddtLL/4APpQuj4VLej2BNzTw+U8IM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=VOaELeC9sXdzbG379c2z+hf3jjNOFgI4AdYBnqsAE0et3OV4zeaV6YaEb3rswkV4/qQ4tOMFrsWymIbVgTsndKs0MOBlKOm52E/EoOcg8f4OBF2EzolX4tLEi8tcmKn+a8qHCKWj2OJPGaNRlmP64cqhvqSdjSfuKeFfksSLzws= Received: by 10.67.29.7 with SMTP id g7mr1324705ugj.1175821956371; Thu, 05 Apr 2007 18:12:36 -0700 (PDT) Received: by 10.66.226.14 with HTTP; Thu, 5 Apr 2007 18:12:35 -0700 (PDT) Message-ID: Date: Thu, 5 Apr 2007 21:12:35 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: [ApacheDS] Definition of a partition In-Reply-To: <390efba50704051503t670125e9i643b7e414630d05f@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_193_18213314.1175821955492" References: <768dcb2e0704041915v1b2c2241pc839c18b8580267f@mail.gmail.com> <390efba50704051503t670125e9i643b7e414630d05f@mail.gmail.com> X-Google-Sender-Auth: 312c744313666505 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_193_18213314.1175821955492 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks a bunch Christine. Sorry for being lazy - I should have added it myself. This release is taking me forever this time though. I guess I am loosing my touch. Alex On 4/5/07, Christine Koppelt wrote: > > I expanded the first section a bit and added it to the "Architectural > Overview" page of the AUG > (http://directory.apache.org/apacheds/1.0/architectural-overview.html). > Further comments or contributions are welcome :-) > > Christine > > > 2007/4/5, Trustin Lee : > > Sounds very good! > > > > Trustin > > > > On 4/5/07, Alex Karasulu wrote: > > > To clarify from previous threads ... > > > > > > Definition > > > ------------- > > > > > > A partition is a physically distinct store for a subset of the entries > > > contained within a DSA (Directory Server/Service Agent A.K.A the LDAP > > > server). The entries of a partition all share the same suffix which > is the > > > distinguished name of the namingContext from which the stored entries > in the > > > partition are hung from the DIT. A partition can be implemented using > any > > > storage mechanism or can even be backed in memory. A partition simply > has > > > to implement the Partition ( 1.5) interface and by doing so can be > mounted > > > in the server at it's suffix/namingContext. > > > > > > The server can have any number of partitions (with any implementation) > > > attached to various namingContexts which are published by the RootDSE > (empty > > > string dn "") using the namingContexts operational attribute. So if > you > > > want to see the partitions served by the server you can query the > RootDSE > > > for this information. > > > > > > Motivation For Terminology > > > ------------------------------------ > > > > > > I decided to use the term Partition to denote this structure in the > server > > > rather than use the term backend. Why? Well to me the backend is > > > everything after the protocol which is basically all of the core. The > > > frontend is the MINA based LDAP protocol service provider. Another > reason > > > for this choice was the fact that a partition is a separate physical > store > > > that separates a subset of the entries. It partitions the DIT, the > > > namespace hence the term "partition" made sense to me. > > > > > > Another crazy reason for this comes from my days as a Linux system > developer > > > while writing device drivers (ahhh those were the days). Anyways I > really > > > like to parallel the concepts of the Linux file system terminology > since it > > > is almost exactly the same concept but in another domain. Basically > file > > > system partitions which can be backed by any kind of random access > store can > > > be mounted at mount points on the file system. To me the mount point > is > > > analogous to the namingContext used to hang the entries stored therein > off > > > the DIT (here I'm relating entries to files). Note this analogy does > > > breakdown in some places but over all it's a descent analogy which > warranted > > > using the name Partition rather than Backend. > > > > > > Alex > > > > > > > > > > > > -- > > what we call human nature is actually human habit > > -- > > http://gleamynode.net/ > > -- > > PGP Key ID: 0x0255ECA6 > > > ------=_Part_193_18213314.1175821955492 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks a bunch Christine.  Sorry for being lazy - I should have added it myself.  This release is taking me forever this time though.  I guess I am loosing my touch.

Alex

On 4/5/07, Christine Koppelt <christine.koppelt@googlemail.com> wrote:
I expanded the first section a bit and added it to the "Architectural
Overview" page of the AUG
(http://directory.apache.org/apacheds/1.0/architectural-overview.html ).
Further comments or contributions are welcome :-)

Christine


2007/4/5, Trustin Lee <trustin@gmail.com>:
> Sounds very good!
>
> Trustin
>
> On 4/5/07, Alex Karasulu <akarasulu@apache.org> wrote:
> > To clarify from previous threads ...
> >
> > Definition
> > -------------
> >
> > A partition is a physically distinct store for a subset of the entries
> > contained within a DSA (Directory Server/Service Agent A.K.A the LDAP
> > server).  The entries of a partition all share the same suffix which is the
> > distinguished name of the namingContext from which the stored entries in the
> > partition are hung from the DIT.  A partition can be implemented using any
> > storage mechanism or can even be backed in memory.  A partition simply has
> > to implement the Partition ( 1.5) interface and by doing so can be mounted
> > in the server at it's suffix/namingContext.
> >
> > The server can have any number of partitions (with any implementation)
> > attached to various namingContexts which are published by the RootDSE (empty
> > string dn "") using the namingContexts operational attribute.  So if you
> > want to see the partitions served by the server you can query the RootDSE
> > for this information.
> >
> > Motivation For Terminology
> > ------------------------------------
> >
> > I decided to use the term Partition to denote this structure in the server
> > rather than use the term backend.  Why?  Well to me the backend is
> > everything after the protocol which is basically all of the core.  The
> > frontend is the MINA based LDAP protocol service provider.  Another reason
> > for this choice was the fact that a partition is a separate physical store
> > that separates a subset of the entries.  It partitions the DIT, the
> > namespace hence the term "partition" made sense to me.
> >
> > Another crazy reason for this comes from my days as a Linux system developer
> > while writing device drivers (ahhh those were the days).  Anyways I really
> > like to parallel the concepts of the Linux file system terminology since it
> > is almost exactly the same concept but in another domain.  Basically file
> > system partitions which can be backed by any kind of random access store can
> > be mounted at mount points on the file system.  To me the mount point is
> > analogous to the namingContext used to hang the entries stored therein off
> > the DIT (here I'm relating entries to files).   Note this analogy does
> > breakdown in some places but over all it's a descent analogy which warranted
> > using the name Partition rather than Backend.
> >
> > Alex
> >
> >
>
>
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
> --
> PGP Key ID: 0x0255ECA6
>

------=_Part_193_18213314.1175821955492--