Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 51189 invoked from network); 9 Oct 2007 21:25:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Oct 2007 21:25:43 -0000 Received: (qmail 44705 invoked by uid 500); 9 Oct 2007 21:25:31 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 44487 invoked by uid 500); 9 Oct 2007 21:25:30 -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 44476 invoked by uid 99); 9 Oct 2007 21:25:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2007 14:25:30 -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 64.233.162.229 as permitted sender) Received: from [64.233.162.229] (HELO nz-out-0506.google.com) (64.233.162.229) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2007 21:25:34 +0000 Received: by nz-out-0506.google.com with SMTP id o1so996265nzf for ; Tue, 09 Oct 2007 14:25:13 -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:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=YAMYncr+8kOH0hDuF9ZgSlT452pmybdegBGoUpgsXnI=; b=RP4PTaHm8pY5Dm4SsvMsn2DHCMEt5hUByRZiLNxCpDt/fMLkW6ipEL4Je8jArc4YbMwX+yI/bR/et1dGvlei/Z0DwBKVJjL80DmCkUIEJMIhFMgGwLlBaSnBzB6SFQovrXWaosJONWaRND0aEvRooJVJH2Af5m8fuaC+nrPtj9w= 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=mzGBLkrf1hLCduUOt0RJu1Ya0RpQu2kZbSnmsDmQxmebpSH7gfjKI8wxEZkVyd697I32FVbdZ4ouqsYegKP97s6dIYIeICUKt99wekXPFdVyF0lAJPLqYECfm3cSB6eDl5iVCJjnGkrev3yzcD90+go6hn0ZZ1+0XfiDKR+DI6I= Received: by 10.115.89.1 with SMTP id r1mr12698299wal.1191965112814; Tue, 09 Oct 2007 14:25:12 -0700 (PDT) Received: by 10.115.76.8 with HTTP; Tue, 9 Oct 2007 14:25:12 -0700 (PDT) Message-ID: Date: Tue, 9 Oct 2007 17:25:12 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: [ApacheDS] Configuration of protocols In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7283_25947257.1191965112807" References: X-Google-Sender-Auth: adc35d5331db6e69 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_7283_25947257.1191965112807 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 10/9/07, David Jencks wrote: > > NTP is pretty darn simple and I'm going to code up a couple of > examples using it so we can better see what we are talking about. NTP is simple and one of the reasons why I picked it for the example. Also as you say it can be used for a simple experiment to see the impact of what we want to do without a massive investment in time. On the other hand although NTP is the easiest to understand the same reasoning may not apply to the other protocols. Enrique understands these best so he might have something to share about it. Knowing that he's not on IRC I made sure he got wind of it by posting it here. There's an extreme danger here of making a mountain out of a > molehill :-) Well the plan was simple: get rid of the configuration beans and directly wire up the components. As I said this was your idea and a damn good one. I just don't want configuration beans floating around with one exception here and one exception there. Let's set a standard pattern to follow and stick to it. Alex ------=_Part_7283_25947257.1191965112807 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 10/9/07, David Jencks <david_jencks@yahoo.com> wrote:
NTP is pretty darn simple and I'm going to code up a couple of
examples using it so we can better see what we are talking about.

NTP is simple and one of the reasons why I picked it for the example.  Also as you
say it can be used for a simple experiment to see the impact of what we want to do
without a massive investment in time.

On the other hand although NTP is the easiest to understand the same reasoning may not
apply to the other protocols.  Enrique understands these best so he might have something to share
about it.  Knowing that he's not on IRC I made sure he got wind of it by posting it here.

There's an extreme danger here of making a mountain out of a
molehill :-)

Well the plan was simple: get rid of the configuration beans and directly wire up the components.
As I said this was your idea and a damn good one.  I just don't want configuration beans floating
around with one exception here and one exception there. 

Let's set a standard pattern to follow and stick to it. 

Alex

------=_Part_7283_25947257.1191965112807--