Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 76798 invoked from network); 2 Mar 2006 19:21:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Mar 2006 19:21:13 -0000 Received: (qmail 53201 invoked by uid 500); 2 Mar 2006 19:21:58 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 53159 invoked by uid 500); 2 Mar 2006 19:21:58 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 53148 invoked by uid 99); 2 Mar 2006 19:21:58 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Mar 2006 11:21:58 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of john.r.fallows@gmail.com designates 64.233.162.200 as permitted sender) Received: from [64.233.162.200] (HELO zproxy.gmail.com) (64.233.162.200) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Mar 2006 11:21:57 -0800 Received: by zproxy.gmail.com with SMTP id q3so517134nzb for ; Thu, 02 Mar 2006 11:21:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=huhpe0M3EOMvzzZ2qyN042uDS4W/qXypj06DVXT0ec2kyiWibhKmg1ZU47NGSxZ2GhqfCXvmhI3unKC8TzWSgMYYwy76kn9WxL5IN/3fdrKEuu23d2myTZQY6GkYh5MDlhgDTS7AJ0TmgCsXn9uV9FnZOpkEYCjxqAcbQR28xZE= Received: by 10.64.253.15 with SMTP id a15mr855947qbi; Thu, 02 Mar 2006 11:21:37 -0800 (PST) Received: by 10.65.73.4 with HTTP; Thu, 2 Mar 2006 11:21:37 -0800 (PST) Message-ID: <83caac420603021121n322ccedcr35def7a9196cd5dc@mail.gmail.com> Date: Thu, 2 Mar 2006 11:21:37 -0800 From: "John Fallows" To: "MyFaces Development" Subject: Re: future vision for MyFaces "commons" In-Reply-To: <564d4f680603010023x7e84e041h5e5d934c0220aa49@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2842_15772219.1141327297092" References: <83caac420602211135j41630269xc14de2dccb88e314@mail.gmail.com> <564d4f680602220032w2d297f36nbd8c2855d09fe875@mail.gmail.com> <2387fbc50602220737j7fc8200ep4098885f7f03d11c@mail.gmail.com> <6dac79b90602221152v352042e7o517d7b272b22e7ff@mail.gmail.com> <2387fbc50602221649qbd44696m2abe98afe5c1ccbf@mail.gmail.com> <8f985b960602230846t2b2d04ebx7272a1821997f4e8@mail.gmail.com> <564d4f680602240307h432566afg30c7607453226601@mail.gmail.com> <83caac420602282123l33e266f0yefd5b26a381a1bb7@mail.gmail.com> <564d4f680603010023x7e84e041h5e5d934c0220aa49@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_2842_15772219.1141327297092 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 3/1/06, Manfred Geiler wrote: > > On 3/1/06, John Fallows wrote: > > We need to define the meaning of "with more caution". > > Terms for future commons utils and helpers: > > * stable API +1. :-) * downward compatibility within major version numbers +1. Backwards compatible at runtime, compile time or both? * separation between API and Impl (to achieve the latter two) +1. Separated by different packages, JARs, or both? * not MyFaces specific +1. These APIs might become candidates for inclusion in future versions of the JSF specification. Would the compilation dependency graph look something like this? [myfaces-commons-api] --depends-on--> [jsf-api] [myfaces-commons-impl] --depends-on--> [myfaces-commons-api, jsf-api] [myfaces-tomahawk] --depends-on--> [myfaces-commons-api, jsf-api] Would the following compilation dependency be avoided? [myfaces-tomahawk] --depends-on--> [myfaces-commons-impl] * make sense for all or many JSF component authors and/or app developers +1. More? Kind Regards, John Fallows. -- http://apress.com/book/bookDisplay.html?bID=3D10044 Author: Pro JSF and Ajax: Building Rich Internet Components, Apress ------=_Part_2842_15772219.1141327297092 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 3/1/06, Manfred Geiler <manfred.geiler@gmail.com> wrote:
On 3/1/06, John Fallows <joh= n.r.fallows@gmail.com> wrote:
> We need to define the meaning = of "with more caution".

Terms for future commons utils and= helpers:

* stable API

+1. :-)

* downward compatibility w= ithin major version numbers

+1.

Backwards compatible at runtime, compile t= ime or both?

* separation between API and Impl (to achieve the latter two)
=

+1.

Separated by different packages, JARs, or both?

* not MyFaces specific

+1.  These APIs might bec= ome candidates for inclusion in future versions of the JSF specification.
Would the compilation dependency graph look something like this?
<= br> [myfaces-commons-api] --depends-on--> [jsf-api]
[myfaces-commons-impl= ] --depends-on--> [myfaces-commons-api, jsf-api]
[myfaces-tomahawk] -= -depends-on--> [myfaces-commons-api, jsf-api]

Would the following= compilation dependency be avoided?

[myfaces-tomahawk] --depends-on--> [myfaces-commons-impl]
<= br>
* make sense = for all or many JSF component authors and/or app developers

+1.

More?
 
Kind Re= gards,
John Fallows.
--
http://apress.com/book/bookDisplay.html?bID=3D10044Author: Pro JSF and Ajax: Building Rich Internet Components, Apress=20 ------=_Part_2842_15772219.1141327297092--