Thanks for your feedback. Java 5 is mainly used (in monitoring) for generics -- collections are type safe and easier to use -- and for java.util.concurrent for mutli-thread performances. Under Java 1.3/1.4 the backport-util-concurrent package provides equivalent support (with some limitations)
Using retrotranslator allow to support users that cannot get a modern Java5+ runtime (like I do), without other ones not to gain the benefict of up-to-date environment. I also contacted Jamon author last year an proposed to contribute : move build to maven2, classes / test separation, plan for a cleaner modular design for a 3.x version, ... The discution was friendly, but not really productive. Build tools and design considerations stands late in Jamon todo list. That beeing said, Jamon allready has a large user base. IMHO, it's succes is related to : - the MonitorFactory.start( name ) method -- can anyone propose simplier ? - the "plug'n play" web UI and web filter It can be used as inspiration for commons-monitoring features, in combination with Moskito that has a nice design and an interesting interval-based monitoring. Nico. 2008/1/24, Siegfried Goeschl <[EMAIL PROTECTED]>: > > Hi Nicolas, > > as a long-time JAMon user and integrator I'm excited about your > incubation project and had a look at your proposal > > +) Regarding JAMon - you probably mean "community driven evolution" > > +) the link to Mosquito is broken > > +) what is the benfit of using JDK 1.5 and retrotranslate the code > (sorry for my ignorance)? > > +) regarding JAMon - I asked the author to move JAMon to Apache but he > politely refused - too much overhead > > Cheers, > > Siegfried Goeschl > > > nicolas de loof wrote: > > Looking a lottle bit more at commons-performance, this component is more > a > > tool dedicated (but not limited) to commons-* develeoper to load-test > > components. It execute some load / multi-threaded tests and relies on > > commons-math for statistics. performance is more a load-test running > tool, > > and monitoring an instrumentation toolkit. > > > > monitoring will have a tiny overlap with commons-math for statistic > > computation (arithmetic mean and standard deviation). > > > > > > > > 2008/1/24, nicolas de loof <[EMAIL PROTECTED]>: > > > >> Thanks a lot for fixing this. I'll configure my svn.. > >> > >> commons-performance is more (AFAIK) a load-test runner. It also > produces > >> statistics, so could overlap for some classes. I'll look at this to > estimate > >> how much this overlap and if / how we could synchronize our work. > >> > >> Nico. > >> > >> > >> 2008/1/23, Niall Pemberton <[EMAIL PROTECTED]>: > >> > >>> On Jan 23, 2008 4:21 PM, nicolas de loof <[EMAIL PROTECTED]> wrote: > >>> > >>>> Hello, > >>>> > >>>> I'm pleased to publish the initial PROPOSAL document for the > >>>> > >>> monitoring > >>> > >>>> component (sandbox) : > >>>> > >>>> > >>>> > >>> > http://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk/PROPOSAL.html > >>> > >>>> Some initial draft code has also been commited in SVN > >>>> > >>>> I've also initiated a design document at > >>>> http://wiki.apache.org/commons/Monitoring > >>>> > >>> Could you configure your svn client's "auto-props" so that it > >>> automatically adds eol style and keywords when you add new artifacts. > >>> I just fixed this for monitoring - but as you can see changing the eol > >>> style created alot of *noise". I also took the liberty of correcting a > >>> couple of mistakes in the proposal and uploading the generated site so > >>> the javadocs are available to view - which should make it easier for > >>> people to have a quick look - should be there in the next 4 hours > >>> after the next sync: > >>> > >>> http://commons.apache.org/sandbox/monitoring/ > >>> > >>> I haven't really looked properly but is there overlap here with the > >>> performance component thats in the sandbox? > >>> > >>> http://commons.apache.org/sandbox/performance/ > >>> > >>> Nial > >>> > >>> > >>>> Nico. > >>>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
