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=BTDNv5qCrCoNFpDhWtocgQCNj1nLA2ylynlGKd0xiwfUW+KIcfe+TwhPIOBw6ed8TP
         gtafq22gyUOT3Wei2O42WgozGIweeaG0dmnj2fPGzeY9ZpMx04lJvNxk21H12EdsEI3Q
         BWn43eknzR1zUZSewBJNI0ha7yuDmfkn5RjmQ=
Message-ID: <4C2E2666.1040409@gmail.com>
Date: Fri, 02 Jul 2010 19:48:22 +0200
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.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Lack of logs for the ACI sunsystem
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

  Hi guys,

I'm going deeper, and start finding some bugs in the subsystem, plus 
many redondant operations.

Sounds good, however, the lack of logs makes it *very* difficult to 
understand what's going on when debugging the whole stuff.

We are now at a point where if we want to give some help to our users, 
we *need* to provide a way to understand what's going on : there is no 
way we will step into the code checking the users' ACIs to see what's 
going wrong everytime a user has a problem with an ACI.

I suggest we add some dedicated loggers, like a ACI_LOG logger, which 
will only gather the ACI related traces. If we want to see what's gone 
wild, we just have to enable this specific logger and check the logs.

We should also have other specific loggers, like :
- encoder/decoder logger (or PDU logs)
- search filter logger (to know which filter is responsible for the 
rejection of an entry)
- SP/Triggers logger
- Ldap session logger (and it should be possible to activate such a log 
for a single session)
- Authentication logger
- backend logger
- replication logger
- cache logger (what is in cache, what is not)

There may be more, but at least, we should think about such a system. It 
may be added later (like for 2.1), and it should be dynamic, but it's 
mandatory IMO.

thoughts ?

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