Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 10626 invoked from network); 29 Oct 2002 08:50:45 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Oct 2002 08:50:45 -0000 Received: (qmail 19814 invoked by uid 97); 29 Oct 2002 08:51:45 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 19751 invoked by uid 97); 29 Oct 2002 08:51:44 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 19735 invoked by uid 98); 29 Oct 2002 08:51:44 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <023801c27f28$56f6cef0$3f1ea8c0@ports.local> From: "Ola Berg" To: "Jakarta Commons Developers List" References: Subject: Re: HMI - Http Method Invocation Date: Tue, 29 Oct 2002 09:51:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I would like to put the initial code, that must be improved and = tested, on > jakarta-commons project. What do you think about? Some "non-binding" (I'm not a committer) thoughts: 1) Smells like it, if the idea is useful enough, should be a jakarta = project of its own 2) if you put your project on hold for a short time and instead help out = with clazz if you like, you will find that your thing should probably = build heavily on existing jakarta-commons components, including clazz. = IIUC, building your thing using clazz is much more trivial than without = it (if the promises from the initial discussion will be fulfilled). 3) Isn't your thing what SOAP and similar techniques do? What can you do = using your stuff that you can't do without it? Why use it? (not asked to = discourage, but to see if there is a foreseeable future for the thing). 4) Have you looked at Avalon? Seems like your thing needs to exist in = some kind of component framework, and Avalon is a pretty good one. /O -- To unsubscribe, e-mail: For additional commands, e-mail: