> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
>
> You mis-understood.
>
> I am not proposing to deprecate it *at this time*, but to
> encourage the developer to think of alternative ways of
> developing their component so that it is not needed.
Yes, but until we do have a replacement - and I do not
think we really reached concensus on it - making anything
public outside of the A5 proposal is just stirring up a lot
of FUD.
We have agreed that it would be nice without a release().
We never really agreed on the replacement. There are some
things that can be formalized so that you may be able to
design components with a need for release() without it
being bad practice. Without investigating those, I do
not think we can make any recommendation at all.
Take the Session for example: It is one way of doing threadsafe
components. But I want to see that it works, that it is
easy to work with, and that it is easily graspable
by newbies before I consider it ready to go and before I see
it as reason enough to deprecate release(). (At the moment
I consider it a tentacled horror.)
I do not want to scare the life out of those committed to
A4 by even hinting that A5 will have less features than A4.
So shove everything into A5 proposal, and wait with any
announcements regarding what developers should think of
until we have a solid understanding of what A5 will be
like. *Then* start the gradual transition.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
