Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 67007 invoked from network); 29 Apr 2002 04:46:11 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Apr 2002 04:46:11 -0000 Received: (qmail 21837 invoked by uid 97); 29 Apr 2002 04:46:19 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 21799 invoked by uid 97); 29 Apr 2002 04:46:19 -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 21781 invoked from network); 29 Apr 2002 04:46:18 -0000 Subject: Re: Instrument questions From: Vincent Tence To: Avalon Developers List In-Reply-To: <1020040348.24675.64.camel@localhost.localdomain> References: <1019520855.31034.41.camel@ localhost.localdomain> <20020423121331.GA2576@expresso.localdomain> <1019603040.6880.67.camel@localhost.localdomain> <1019605339.6882.108.camel@localhost.localdomain> <3CC66E87.3080902@tanukisoftware.com> <1020009967.2724.44.camel@localhost.localdomain> <1020040348.24675.64.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 29 Apr 2002 00:49:05 +0000 Message-Id: <1020041345.25994.71.camel@localhost.localdomain> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Looking at the javadoc of InstrumentSample, it suggests that we could add InstrumentSamples to an Instrument as a result of a request from an InstrumentClient. Does that mean we should add addInstrumentSample() and removeInstrumentSample() to InstrumentDescriptor interface? Thanks, Vincent On Mon, 2002-04-29 at 00:32, Vincent Tence wrote: > I'm throwing in some more instrument questions: > > 1. Clients access the Instrumentables through InstrumentableDescriptors > via the InstrumentClient. In the DefaultInstrumentManager, shouldn't we > reset the optimized arrays m_instrumentableProxyArray and > m_instrumentableDescriptorArray when a new InstrumentableProxy is added > in registerInstrumentable() (like we do in configure())? That way we > could add Instrumentables - not declared in the config - after configuration, > which would be visible to clients. > What was your idea behind registering Instrumentables not declared in the config? > I'm not sure to understand this correctly. > > 2.To add new InstrumentSamples that have not been declared at configuration stage, > I would use the addXXXListeners() method on the InstrumentDescriptor in my client code > and pass it an InstrumentSample. But those samples would only be visible to my client > - as opposed to those added via addInstrumentSample() - correct? > (btw, is addInstrumentSample() in InstrumentProxy public on purpose?) > I may want to do that to let the administrator specify custom samples when the application is running. > Is that possible? > > Thanks, > Vincent > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: