On Wednesday 12 December 2001 10:26 am, you wrote:
> Purposeful Design Constraints
>
> 1) Profilable only provides a simple integer sample.
Why is that a purposeful constraint? That constraint is directly responsible
for your issue #1, multiple points per component. I think issue #1 is huge
because for a pool you many want to know current size, defined max & min, max
it has ever grown to, etc. I think multiple points/component would be the
norm, rather than the excepetion.
How about changing Profilable to
interface Profilable
{
/**
* A list of the sample points that this component exposes.
*/
String[] getSamplePoints();
/**
* Obtain the sample. All samples are an integer, so the profiled objects
* must measure quantity (numbers of items), rate (items/period), time in
* milliseconds, etc.
*/
int getSample(String point);
}
Otherwise I think the proposal looks good! :)
-pete
--
peter royal -> [EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
