Ron Blaschke wrote:
Ross Gardler wrote:
Ron Blaschke wrote:
Ross Gardler wrote:
Most things are straightforward. I'm only puzzled by the mix of input
plugin (ie, take data from the profiler data store and render it) and
internal plugin (ie, profile stuff and store results in profiler data
store). Can a plugin be both, input and internal?
An internal plugin sitemap gets mounted before anything else is done. So
you can indeed make an internal plugin be both input and output as well
as internal. It is easy to break everything with internal plugins, much
harder with input and output plugins.
Good, so this shouldn't be too hard, either.
Today is Forrest-Tuesday [1] you can find us on irc.freenod.org #for-oct
if you need any pointers.
The one thing left that keeps me from getting started is that I don't
know how to contribute the plugin. I don't have any commit rights to
Forrest, so I guess I am limited to (1) create an issue and attach my
changes there, or (2) host the plugin myself. The names would be
org.apache.forrest.plugin.internal.cprofile or
org.rblasch.forrest.plugin.internal.cprofile, respectively.
Ron and I are discussing this on IRC, you can see the logs at 20:09
(http://casa.che-che.com/~bot/forrest/forrest.log.04Oct2005)
This includes the idea of making this profiling plugin into a wider
ranging test plugin. Worth a read (or contribution if you are around at
the right time).
Ross
