Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: cxf-dev@incubator.apache.org
Subject: Re: This caching/startup speedup project
Date: Wed, 5 Mar 2008 09:59:22 -0500
User-Agent: KMail/1.9.7
Cc: "Christian Vest Hansen" <karmazilla@gmail.com>
References: <61b5d9410803050404m265b3911ke19f4b2b7d0a365@mail.gmail.com>
 <90622e530803050556h69ecf20au2aaf46582379bc36@mail.gmail.com>
In-Reply-To: <90622e530803050556h69ecf20au2aaf46582379bc36@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803050959.22722.dkulp@apache.org>


JProfiler does grant licenses to opensource projects providing we provide 
a "thank you" link back to them which, in general, we're OK with.   
Several projects have done that:

Example:
http://ws.apache.org/axis2/thanks.html

Note: intellij does the same thing.

One important aspect is that the tool must be available for all the 
committers in the community to work on the project.   Thus a "project" 
license.   Some tools will say "we'll give you 5 licenses" or something.  
I'm not OK with that.   JProbe tends to go the 5 licenses route.

The next trick is managing the license key itself (if there is one).   We 
cannot put it up on the public website so, most likely, someone would 
need to be the "key master" and send them out to community folks on 
demand via email.   

Either that or we could just take everyone's public gpg keys, encrypt 
them as files for each person, and check them into svn someplace...  :-)

Dan


On Wednesday 05 March 2008, Christian Vest Hansen wrote:
> Yourkit [1] is used by a number of other open source projects, but I
> haven't tried it. I personally like the JProfiler [2] but I don't know
> if they give licenses to open source projects.
>
> [1] http://www.yourkit.com/
> [2] http://www.ej-technologies.com/products/jprofiler/overview.html
>
> On 3/5/08, Benson Margulies <bimargulies@gmail.com> wrote:
> > I might be willing to take a run at this. Can someone tighten up the
> > idea a bit? If we were to cache service models, what would we
> > key/invalidate the cache against? How do we know that we
> > subsequently need 'exactly the same one'.
> >
> >  For that matter, what about some profiling to make sure that there
> > isn't something we could tighten up?
> >
> >  Anyone have a favorite tool for that purpose?


-- 
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog