From dev-return-21783-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Oct 01 16:37:12 2007 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 16345 invoked from network); 1 Oct 2007 16:37:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Oct 2007 16:37:11 -0000 Received: (qmail 4189 invoked by uid 500); 1 Oct 2007 16:37:01 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 4142 invoked by uid 500); 1 Oct 2007 16:37:00 -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 4131 invoked by uid 99); 1 Oct 2007 16:37:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2007 09:37:00 -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 (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.132.251 as permitted sender) Received: from [209.85.132.251] (HELO an-out-0708.google.com) (209.85.132.251) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2007 16:37:02 +0000 Received: by an-out-0708.google.com with SMTP id c31so485067ana for ; Mon, 01 Oct 2007 09:36:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; bh=rECR+1Ikhq8gd/epREWN+CtPytd4Yb0AQjUhNnsnmDA=; b=r3EsOrykZGIX0PKBpYNom87004wphW+DgU8RlzUcGtVLy0sRMxge8dyALVaO1tiV+6+zonmaoOf7di2vkhebJn47vloezyVrMUpmqawzAHNALG9kLWXEmC1IDIi0Urz7Kw8Fmn/S5B7vUJohUkOHikI32Zeuaa0VEw4829PWQAg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=j9xC6b0lZieJgVdpX3ccwFjMoy/LY9/Lpcb/+Iz34W4QAclEUlN6tjkj758VOnThWx05zQfyYuKZBTyOFP9UKDzj+TER89O8Co/1wTipxO+dPzxTWclcRCBnEsx69No+sjhtlPPOEkouPE/k9KEVPEVWQWtRU4WT8XQaaEx76xw= Received: by 10.114.156.1 with SMTP id d1mr827640wae.1191256599800; Mon, 01 Oct 2007 09:36:39 -0700 (PDT) Received: by 10.115.76.8 with HTTP; Mon, 1 Oct 2007 09:36:39 -0700 (PDT) Message-ID: Date: Mon, 1 Oct 2007 12:36:39 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: [ApacheDS] Things to consider for big bang refactoring MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11067_12583594.1191256599796" X-Google-Sender-Auth: f7e373a70d84e294 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_11067_12583594.1191256599796 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, The bigbang branch where we are heavily refactoring the server is going very well. The changes that we're making are cleaning up a lot of questionable glue code that has cluttered the server. We can thank Chris and David Jencks for being persistent on this matter because the rewards of using Spring as they suggested are huge. Regardless this email is not about getting status out although that's good too. I wanted really to point out to those who had issues with the existing architecture in trunk that now is the best time to hale us on those problems to be considered in the big bang. Anything can be done now since we're getting aggressive with changes. If we do not have the issues sited in the past in mind in the refactoring then we might cause greater problems in the future. I know some issues were pointed out regarding virtualization. Also there are other matters like a global cache. Perhaps we can list these issues in this thread and consider what needs to be done to at least provide hooks for these subsystems even if they are not implemented in totality. Here's my short list: virtualization - virtual and calculated attributes, entries, and backends global cache - we need one but how do we best enable one monitoring - JMX? security manager - sandboxing stored procedure code authorization identity - separation of authenticated and authorized identities transactionality - for server local transactions and not LDAP transactions or distributed transactions locking and synchronization OSGi concerns There is no way one person can keep tabs on all these factors while we are in the big bang. We probably cannot do it all together either. We probably cannot list everything either. However it's worth trying even if it is just a listing of general concerns: it's worth just trying to make sure we can make the best of this refactoring opportunity. Thanks, Alex ------=_Part_11067_12583594.1191256599796 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all,

The bigbang branch where we are heavily refactoring the server is going very well.  The changes that we're
making are cleaning up a lot of questionable glue code that has cluttered the server.  We can thank Chris
and David Jencks for being persistent on this matter because the rewards of using Spring as they
suggested are huge.

Regardless this email is not about getting status out although that's good too.  I wanted really to point out
to those who had issues with the existing architecture in trunk that now is the best time to hale us on those
problems to be considered in the big bang.  Anything can be done now since we're getting aggressive with
changes.  If we do not have the issues sited in the past in mind in the refactoring then we might cause greater
problems in the future.

I know some issues were pointed out regarding virtualization.  Also there are other matters like a global cache.
Perhaps we can list these issues in this thread and consider what needs to be done to at least provide hooks
for these subsystems even if they are not implemented in totality.  Here's my short list:

virtualization - virtual and calculated attributes, entries, and backends
global cache - we need one but how do we best enable one
monitoring - JMX?
security manager - sandboxing stored procedure code
authorization identity - separation of authenticated and authorized identities
transactionality - for server local transactions and not LDAP transactions or distributed transactions
locking and synchronization
OSGi concerns

There is no way one person can keep tabs on all these factors while we are in the big bang.  We probably
cannot do it all together either.  We probably cannot list everything either.  However it's worth trying even if
it is just a listing of general concerns: it's worth just trying to make sure we can make the best of this
refactoring opportunity. 

Thanks,
Alex

------=_Part_11067_12583594.1191256599796--