On Monday, May 2, 2011 10:33:59 AM UTC-4, pbreit wrote: > > Right, but I get no benefit then.
If you've got models that are needed by multiple controllers, then there's no benefit to be had -- all your models will have to be run on every request anyway. The benefit comes if you've got some models that are only needed for specific controllers or functions -- in that case, you run only the models you need for the specific request, and that can save some time/memory. If you need a particular model only for a few functions, but those functions are scattered across multiple controllers, then yes, this new change will not help -- for that, we'd need a more sophisticated router functionality. I take it, though, that the router approach would likely involve more effort to design and implement, so what we've got now is a quick change that will provide nice benefits for a lot of use cases, even if it's not yet as flexible as a full router based approach. Anthony
