Hello Kees Jan, On Wed, Nov 19, 2008 at 8:25 PM, Kees Jan Koster <[EMAIL PROTECTED]> wrote: > Dear Leon, > > Oh, don't be so dramatic. There is a whole world out there of smaller > companies that have one or two Tomcat servers in production, running on the > cheapest shared server environment they could find. This product targets > companies that have two or three developers, one of whom has been pressed > into doing the admin role on the side.
yes, but why should they give their very sensitive data into the hand of someone? You understand that tomcat operation profile provides perfect opportunity for a potential attacker or competitor? Especially when there are tools which does the same without giving the data away. > > I apologize if the operational model of Java-monitor startled you. That was > not my intention. It works this way because that takes the care and feeding > of the monitoring platform away from the user. Some people like that while > others, such as yourself, prefer not to work like this. Why dont you just supply another web/app which collects the data locally in the customers environment? > > Even in large companies, Java-monitor has its place. I spoke to one of my > users this week and he tells me that he uses Java-monitor on the test > machine because the process of getting JBoss performance statistics out of > their hosting company takes days. I like it because I can check the status > of my servers from my iPhone. Again, there are tools which perform the same or more without giving the data to potential competitor or hacker. Check lambdaprobe (tomcat level) or moskito (application level). Regards Leon > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
