Hi, we hit some performance issues using the tapestry IoC. The problem is that we have legacy apps where we do need to do a lot of registry look-ups - takes a while to rewrite everything to have services injected via constructors everywhere. In our particular case we have a few hundred services and in one instance a static call was replaced with a registry look-up and a call on the service. It turns out that a registry look-up is rather slower than we expected.
A colleague has looked into this and says: "We are having some performance issues with the getService() method in the 'RegistryImpl' class. Looking at the source code it seems that there are some linear list searches going on in there that could perhaps be replaced by more efficient map lookups, if possible." Has anybody looked into the performance of the IoC? Thanks, Adriaan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
