Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 51197 invoked from network); 17 Sep 2002 09:13:36 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 17 Sep 2002 09:13:36 -0000 Received: (qmail 3659 invoked by uid 97); 17 Sep 2002 09:14:23 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 3601 invoked by uid 97); 17 Sep 2002 09:14:22 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 3583 invoked by uid 98); 17 Sep 2002 09:14:21 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Tue, 17 Sep 2002 11:04:35 +0200 To: Avalon Developers List Subject: Re: Add support for instrumentation ? Message-ID: <20020917090434.GA30452@fztig938.bank.dresdner.net> References: <20020913111838.GB3999@fztig938.bank.dresdner.net> <038901c25b25$86122990$0100a8c0@MAUCHI> <20020913131802.GC9892@fztig938.bank.dresdner.net> <3D82920C.70506@tanukisoftware.com> <20020916105742.GA7637@fztig938.bank.dresdner.net> <3D85CD59.6030500@tanukisoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <3D85CD59.6030500@tanukisoftware.com> User-Agent: Mutt/1.4i From: Marcus Crafter X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Leif, On Mon, Sep 16, 2002 at 09:23:53PM +0900, Leif Mortenson wrote: > Marcus, > Looks like you have been doing good work over there. I am excited > to see > so much interest in the instrumentation tools. The instrument package is > good and stable and I believe the instrument-manager package is there as > well. I have been working on the client on and off as I get time. It > has been > getting more and more stable, but still has a few features to implement. > (Mainly documentation!) Thanks. Yes, I'm also excited to see instrumentation support in Cocoon. Hopefully it will flow over into Avalon as well with further improvements to the client and server, which would be great :) > As for JMX, I'll admit to being no where near a JMX expert. I read over > the sun specifications a year or so but never had a chance to get into > playing with it much. I haven't looked too deeply into it either. I'll have a look at the specs too when I get some spare time. > There may be some overlap (??) , but the goal with the instrument code > was to write something very lightweight that developers could feel > comfortable > integrating throughout their code without worrying about performance. After > all one of the things the instrument code is supposed to do is help > understand > how instrumented code is working to help improve performance. Yes, I agree. > The instrument manager supports pluggable connectors. Would adding > a JMX connector make sense? That way all of the profiling data could be > accessed via JMX. Perhaps it might ? I think I need to learn more about JMX before being able to say though. One thing I'm interested in is having a SOAP connector, ie. to be able to deliver the profiling data via a SOAP request. > Let me know if there is anything standing in your way with getting > this into cocoon. Well, it's already in. I checked the changes into CVS yesterday. :) Cheers, Marcus -- ..... ,,$$$$$$$$$, Marcus Crafter ;$' '$$$$: Computer Systems Engineer $: $$$$: ManageSoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$, _/\ &&:' 60327 Frankfurt Germany ' /( &&& \_&&&&' &&&&. &&&&&&&: -- To unsubscribe, e-mail: For additional commands, e-mail: