> From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
> Berin Loritsch wrote:
>
> Ok, lets take the DefaultComponentManager.release() operation - the
> implementation currently is the following:
>
> public void release( final Component component )
> {
> }
>
> This is the framework reference implementation of release.
> Yes - it is
> easy to understand, yes - its easy to use.
(Just noticed: It is dead wrong as well. The dispose() method is
not called for SingleThreaded components.)
> Could we come up with something that is better?
> Yes - remove it and delivery something better in
> the right level of abstraction.
Well, what would that be?
If you claim to want a grounded debate, then for the love of God,
can you come up with something better that *is* at the right level
of abstraction and at the same time *is* easy for our users?
All proposals so far to that effect have either been:
1) not workable
2) pushing way too much responsibility on to
the component writer
3) too complex to be understood
You can argue that "easy" means "just like ECM" and you'd be
partially right. But whether your reference point is ECM or not,
ECM has some very good features that many people have found useful
and that would be removed if release() is removed.
You can argue for removal of those features from the framework,
but then I'd like you to give me a replacement for those features.
I'm with Berin on this one.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
