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 (nike.apache.org: domain of elecharny@gmail.com designates
 74.125.82.44 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=LEF2+MCQp+ZC6HLZLq542ERG+T113GZsP6TueNMxI4EINdZcYHcdB5o+yg6tGM35a8
         M8JsnqISzqYnzwNt7L5GSRiFUcrBdLH3k0x3p3tYtYz1hkxyq6lLEkCbddD0Sekgx7qm
         K76YmJTsjeAjvYoMSMHsWdx2qaqdG9Bl5qeYk=
Message-ID: <4D0B67A1.4040208@gmail.com>
Date: Fri, 17 Dec 2010 14:37:37 +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: [AdminPoint] Add operation
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Here is the description of an Add operation, and how it's handled by the 
AdministrativePoint handler. The parts between >>>--- and ---<<< are 
pseudo code.

+--+
|AP|
+--+

We have to deal with three cases :
- the AP has a parent AP (IAP or SAP, it's irrelevant) and no 
subordinate IAP
- the AP has a parent AP but some subordinate IAPs
   in this second case, we have to change the IAPs seqNumber to reflect 
the change in entries relationship, recusively.
- the AP has no parent AP

The second case is the most complex.

 >>>-------------------------------------------
for each AP role
   get a new seqNumber, add it to the AP(role)
   update the AP(role) cache

   if hasParentAP( AP(role) )
     then
       if hasSubordonateIAP( AP(role) )
         then
           for each subordinate IAP(role) (and their own subordinates)
             modify the subordinate IAP(role) seqNumber with the new 
seqNumber
             store the IAP(role)
           done
done

continue down the chain
-------------------------------------------<<<


+--------+
|Subentry|
+--------+

We can't add a subentry if the immediate parent is not an AP and if the 
parent AP does not have the same role (or of the parent  is an IAP and 
there are no higher parent with the same role).

Otherwise, adding a subentry is just a matter to update the parent's AP 
seqNumber (and all the hierarchy up to the first SAP if it's an IAP)

As a subentry is only associated with one single role, we don't have to 
loop on all the roles

 >>>-------------------------------------------
check the parentAP for the role

get a new new seqNumber

update the parentAP and all its IAP subordinate with the same role with 
the new seqNumber

continue down the chain
-------------------------------------------<<<

+-----+
|Entry|
+-----+

When we add an entry, we have to check if it depends on an AP for each 
roles. If so, we have to add the AP seqNumber into the entry, and add 
references to all the subentry it is related too.

 >>>-------------------------------------------
for each role
   for each parent AP(role)
     get the parentAP(role) seqNumber, store it into the entry

     for each subentry associated with the AP(role) do
       if the entry is part of the subtree
         then add the subentry entryUUID into the entry references
     done
   done
done

continue down the chain
-------------------------------------------<<<


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