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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
