Leif Mortenson wrote:
If integrated at this level, the user of the container can get a huge benefit from
Instrumentation without ever making use of the API themselves.
I, for one, would be ecstatic to see the container internals instrumented. I agree, Leif, this would provide a great benefit. Thinking out loud here, but I wonder if the container utilizes the instrumentation package internally, could it be *handed* off to the component via the Context so that (to the user) it would appear like seamless instrumentation of both the container and component?
Both Fortress and ECM will automatically register any Components which implement the
Instrumentable interface. Unlike LogEnabled, it is setup so that a container does not need
to support the interface.
When writing a component that instrumentable, you make your code use the instruments
whether the container supports them or not. The code is optimized so that this does
not cause a performance hit. Even when a component is registered with an
InstrumentManager, there is only a performance hit if and only if a particular instrument
is actually being monitored. Even then, the hit is very small, although the later does involve
a single synchronization block.
In addition to the Instrumentable interface, a second InstrumentManageable interface
exists for components which need to obtain their own reference to the
InstrumenManager. I use this for my Jetty component to provide instrumentation
functionality to servlets etc. It is also useful for nested containers etc.
So if I understood your comment, there should be no need to make use of the Context.
As it is, everything already appears to be quite seamless.
Cheers, Leif
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
