Return-Path: Delivered-To: apmail-james-general-archive@www.apache.org Received: (qmail 52976 invoked from network); 31 May 2005 16:25:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 May 2005 16:25:30 -0000 Received: (qmail 17731 invoked by uid 500); 31 May 2005 16:25:18 -0000 Delivered-To: apmail-james-general-archive@james.apache.org Received: (qmail 17519 invoked by uid 500); 31 May 2005 16:25:17 -0000 Mailing-List: contact general-help@james.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@james.apache.org Delivered-To: mailing list general@james.apache.org Received: (qmail 17372 invoked by uid 99); 31 May 2005 16:25:16 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=FORGED_MUA_OIMO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from devtech.com (HELO mail.devtech.com) (66.112.202.2) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 31 May 2005 09:25:12 -0700 Received: from localhost ([127.0.0.1]) by mail.devtech.com (JAMES SMTP Server 2.2.1-dev) with SMTP ID 15 for ; Tue, 31 May 2005 12:24:16 -0400 (EDT) From: "Noel J. Bergman" To: Subject: RE: mailet api list Date: Tue, 31 May 2005 12:24:09 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Danny Angus wrote: > I only have one further comment, which is that you say: > "I presume that the list would be for discussing the API, not > implementation." > Which is fine per-se but does mean that the few interfaces and classes in > org.apache.mailet will be designed on one list and developed on another. No, I agree that anything that is coded in org.apache.mailet should be part of the API, and thus discussed on that list (even though we'll leave commits where they are for now). That may mean a change over time to just have interfaces, but for now ... --- Noel