Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 25277 invoked from network); 20 Dec 2004 13:08:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Dec 2004 13:08:27 -0000 Received: (qmail 10943 invoked by uid 500); 20 Dec 2004 13:04:21 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 10915 invoked by uid 500); 20 Dec 2004 13:04:20 -0000 Mailing-List: contact directory-dev-help@incubator.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 directory-dev@incubator.apache.org Received: (qmail 10901 invoked by uid 99); 20 Dec 2004 13:04:20 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from ensim1.25oz.com (HELO ensim1.25oz.com) (216.40.203.202) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 20 Dec 2004 05:04:12 -0800 X-ClientAddr: 66.208.12.130 Received: from [192.168.0.81] ([66.208.12.130]) (authenticated bits=0) by ensim1.25oz.com (8.12.10/8.12.10) with ESMTP id iBKDTwSt013032 for ; Mon, 20 Dec 2004 08:29:59 -0500 Message-ID: <41C6CDBB.6080207@d-haven.org> Date: Mon, 20 Dec 2004 08:03:55 -0500 From: Berin Loritsch User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [mina] Current status References: <768dcb2e04121902037b8217f9@mail.gmail.com> <41C5C167.7020308@bellsouth.net> In-Reply-To: <41C5C167.7020308@bellsouth.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Alex Karasulu wrote: > Berin, Trustin wdyt about using similar constructs in SEDA or even > making these filter interfaces common (shared across sedang and mina) > in the protocol API packages? Is it worth doing that? Me, I think so. Trustin and I exchanged IM addresses so that we can discuss just that. I'd like to come up with a decent API, and there are good things that come from both approaches to network development. So, the big question is what is the best blend. I'm sure we will come up with something good. -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook