We shouldn't do it. People would hat Tapestry for it. On Mon, Oct 11, 2010 at 6:49 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
> This came up during my training class this week. > > What would be the repercussions if Tapestry included a start-up filter > that "reported" the application startup back to some central location, > so that we could get some idea of where and how Tapestry is being > used? Obviously, this would be documented, in such a way that it > would be easy to turn off for the privacy-minded. > > It would be interesting to know how many apps are running in the wild, > and details about how many pages & components & services, JVM > version, and OS and hardware configuration. > > Asking people to do this manually is a non-starter, I'm constantly > surprised by people telling me they are using Tapestry in visible > places. > > Thoughts? > > > ---------- Forwarded message ---------- > From: Alessio Gambi <agamb...@gmail.com> > Date: Mon, Oct 11, 2010 at 9:18 AM > Subject: Re: Monitoring/statistics > To: Tapestry users <users@tapestry.apache.org> > > > 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 <hls...@gmail.com> 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. > > > > Obviously, it's a bit late for 5.2 ... it may be time to cut a 5.3 dev > > branch off the current 5.2 code base. > > > > On Sun, Oct 10, 2010 at 2:05 PM, Josh Canfield <joshcanfi...@gmail.com> > wrote: > >> I'm thinking about rolling my own generic monitoring/statistics solution > for > >> tapestry 5 and I figured I should see if something is out there already > >> before I spent too much time on it. > >> > >> This is to be used in production and connected to an external monitoring > >> system, probably via JMX, but we might be flexible. > >> > >> Anything come to mind? > >> > > > > > > > > -- > > Howard M. Lewis Ship > > > > Creator of Apache Tapestry > > > > The source for Tapestry training, mentoring and support. Contact me to > > learn how I can get you up and productive in Tapestry fast! > > > > (971) 678-5210 > > http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Best regards, Igor Drobiazko http://tapestry5.de
