Hi All,
Hope all is well.
Just been looking through the Profiling interfaces in
scratchpad which look quite nice. I've come up with a couple of
questions though:
1. What should the intended calling order for the Profiler class be ?
ie:
// create profiler
Profile p = new Profiler();
...
// add profilables
p.add(myProfilable1);
p.add(myProfilable2);
...
p.add(myProfilableN);
// add report
p.report(new CSVProfileReport("report.csv"));
// start reporting (reporting runs in a separate thread)
p.start();
...
p.stop();
Should there be a start()/stop() method in the Profiler interface, or
left up to the implementation ?
2. Each Profilable object needs some sort of identifying name - Profiler.add()
actually documents a named argument which seems to have been removed.
Should there be a Profilable.getProfilableName(); method or something similar
added to Profilable's interface ?
3. ProfileReport.addGroup() has me confused.
What is the concept of a 'group' here ? Do the groupName and subgroupName
parameters represent the Profilable object name, and the names of its
Profilable points ?
Or the name of the Profilable object and it's children Profilables ? (in which
case where are the profilable points printed ?).
Or something else entirely ?
What if it was:
void addProfilable(Profilable profilable);
An implementation could then get the name of the profilable object,
along with its profiling points and child profilables if any ?
Any thoughts/comments would be much appreciated ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
