Right, I'm back and off the crack. ;) > From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > This is completely consistent with the A5 approach. What I > like is the > fact that Leo is suggesting the pooled resource management > (refered to > above as ComponentManager) can be formalized at the framework level.
Yes, that is my intention. ComponentPool is not a good name, as the interface must work with the A5 equivalent of A4 SingleThreaded components. ComponentHandler or ComponentFactory are better, although I think ComponentManager is the best. When you convert an A4 app to A5, if the interface is there, references to it will be used almost exactly in the same places as you used A4 ComponentManager before. So I would call it ComponentManager. /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
