Re: Monitoring/statistics

2010-10-12 Thread Josh Canfield
> Why dont reuse already existing projects? Reuse is a definitely a goal for me personally. I'm thinking that there will be a facade though so that if I choose Simon, or JAMon or Perf4j that decision won't be pushed down into framework users. I'm sort of deciding between JavaSimon and Perf4j at th

Re: Monitoring/statistics

2010-10-12 Thread Massimo Lusetti
On Mon, Oct 11, 2010 at 6:05 PM, Howard Lewis Ship wrote: > I've been thinking about this kind of thing as well; having a JMX bean > for each Page instance and tracking number of render requests, number > of event requests, number of ajax even requests, and ellapsed > processing time for each. >

Re: Monitoring/statistics

2010-10-11 Thread Anton Gavazuk
Why dont reuse already existing projects? http://code.google.com/p/javasimon 2010/10/11 Alessio Gambi > Hi, > Please think also about some way to obtain (meta) statistics about Tapestry > itself. Something that can be used to track how many people are actually > using tapestry as platform for th

Re: Monitoring/statistics

2010-10-11 Thread Alessio Gambi
Hi, Please think also about some way to obtain (meta) statistics about Tapestry itself. Something that can be used to track how many people are actually using tapestry as platform for their applications. -- Alessio On 11-ott-2010, at 18:05, Howard Lewis Ship wrote: > I've been thinking about

Re: Monitoring/statistics

2010-10-11 Thread Howard Lewis Ship
I've been thinking about this kind of thing as well; having a JMX bean for each Page instance and tracking number of render requests, number of event requests, number of ajax even requests, and ellapsed processing time for each. Obviously, it's a bit late for 5.2 ... it may be time to cut a 5.3 de