Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 19770 invoked from network); 12 Mar 2002 19:59:02 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Mar 2002 19:59:02 -0000 Received: (qmail 10778 invoked by uid 97); 12 Mar 2002 19:57:45 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 10736 invoked by uid 97); 12 Mar 2002 19:57:43 -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 10614 invoked from network); 12 Mar 2002 19:57:37 -0000 Message-Id: <200203121957.g2CJvZp06262@mail012.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Avalon Developers List" Subject: Re: New AltProfile package Date: Tue, 12 Mar 2002 09:21:44 +1100 X-Mailer: KMail [version 1.3.2] References: <20020307125317.GA10366@fztig938.bank.dresdner.net> In-Reply-To: <20020307125317.GA10366@fztig938.bank.dresdner.net> X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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, Love to see this written down and put in a package.html doc :) Do you want to volunteer ? :) On Thu, 7 Mar 2002 23:53, Marcus Crafter wrote: > Hi Leif, > > Well, after a short interlude with our project work here, I was > finally able to have a look at your altprofile code. > > Nice stuff. It's certainly a lot further advanced than the code > I'd written. Well done. > > I've tried to get my head around your design, etc. Please tell > me if the following analysis is right: > > ----------------------------------------------------------------- > > The profile manager maintains a list of profilable objects, > registered either automatically by the profilable component > manager, or manually via a registerProfilable() method on the > manager itself. > > Each profilable exposes 0 to many profile points which maybe of > type 'value', or 'counter'. > > Upon registration with the profile manager, a profilable proxy > is created which manages profile point proxies across threadsafe > and non thread safe components. > > Profile point proxies let you register listener classes for > updates from the profile points themselves. The listeners can be > implementors of a lower level ProfilePointListener class, or > high level Sample classes. > > The profile manager can be configured to automatically create a > set of listeners (samplers in this case) for particular profile points > on a particular profilable. Samplers configured in this way can > be accessed via the profile manager. The gui reporter essentially > iterates through the list of available samplers when building > it's menu's. > > When profilables update their profile points, each listener is > informed of the update, along the lines of the observer pattern. > > The profiler manager exposes an array of all profilable descriptor > objects, which in turn expose an array of all profile point > descriptor objects, which offer reporting tools a way at > accessing the profilable objects this manager manages and > registering listeners. > > ----------------------------------------------------------------- > > Does this analysis sound right ? Is there anything I've missed ? I do > have a few comments, but I want to make sure I've understood everything > first. :-) > > Cheers, > > Marcus -- Cheers, Pete *-----------------------------------------------------------------------* PROGRAM: n. a magic spell cast over a computer allowing it to turn one's input into error messages. v.t. to engage in a pastime similar to banging one's head against a wall, but with fewer opportunities for reward. *-----------------------------------------------------------------------* -- To unsubscribe, e-mail: For additional commands, e-mail: