Ok, we have many +1 from cocoon committers, we have only one +1 from an avalon committer (myself :( ) and no other vote from other avalon committers.
So, this is situation is a little bit difficult. But as we don't have a -1, "lazy consensus" applies. So, if noone complains in the next hours I will remove the proxy code. Carsten Carsten Ziegeler wrote: > > Volker found recently a hugh performance problem in the > current DefaultComponentFactory in Excalibur. > > You can find more information here: > http://marc.theaimsgroup.com/?t=106779872700001&r=1&w=2 > > http://marc.theaimsgroup.com/?t=106802136600002&r=1&w=2 > > I propose to remove the ComponentManagerProxy as this is > a) a performance killer and b) not soo useful as it might > look. > > In some situations the ComponentManagerProxy is able to > release components that the developer has forgotten to > release - but only in some cases. As the general rule > when using excalibur is, to always release components, > removing the ComponentManagerProxy doesn't do any > harm, but provides greater performance. > > Please cast your votes: > > Carsten > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
