On Fri, 14 Dec 2001 08:08, Berin Loritsch wrote:
> The problem arrizes with how do we determine what the parent ProfilePoint
> is?
Same way as Logger, ComponentManager, Context, etc does.
> It does not make sense to have a Pool's max active ProfilePoint be the
> parent of an ObjectFactory's number of created instances ProfilePoint.
> They represent something completely unique.
eh? Could you rephrase ? ;)
> If this is going to scale, we *have* to make it happen at the Profilable
> level. Remember, this is IoC, so a child Profilable is not going to have
> access to the Parent's ProfilePoints at all.
and a child Profilable should not directly create its top ProfilePoint, IOC
and all
> > and the name would be set via
> >
> > parent.getName() + myName
> >
> > however the method getName() would be protected, package or private
> > access (depending on what we could get away with) and done in the case
> > class.
>
> I don't like this, as it is Subversion of Control. A child should not have
> a direct reference to it's parent. The name has to come from being
> assigned, or we trust the Component to use proper "divination" to generate
> a meaningful name.
why can't it operate like all our other hierarchial aspects?
--
Cheers,
Pete
-----------------------------------------------------------
If your life passes before your eyes when you die,
does that include the part where your life passes before
your eyes?
-----------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
