Shared resources and routing will need to be bootstrapped regardless of which module was accessed in the request.
If the shared resource is used by other modules (or the default one), you'll need to bootstrap it. To follow DRY, it'd be best to only write that bootstrap code once. If you are concerned about pages that don't use the resource, then use a lazy-loading approach. BTW, Zend_Db lazy-loads the connections by default so there is very little overheard in bootstrapping all your db connections for each request. The same is true for the cache manager resource (all caches are lazy-loaded). As for routes, you'll need to bootstrap the module's routes in order to match them, so you'll need to bootstrap them on every request (regardless if they matched). You can't have your application figure out which module to load and then bootstrap its routes. -- *Hector Virgen* Sr. Web Developer Walt Disney Parks and Resorts Online http://www.virgentech.com On Mon, Aug 30, 2010 at 10:21 AM, Rafael <dexter...@hotmail.com> wrote: > > Because I still need controller routing and some shared resources like > sessions...It will be a portal > > Em 30/08/2010 14:06, Саша Стаменковић escreveu: > > I don't see need for modules in that case, why not making it separate app? >> >> Regards, >> Saša Stamenković >> > >
