[support] problem with too many modules
Chris Johnson
cxjohnson at gmail.com
Wed Jan 7 16:32:55 UTC 2009
The following 2 modules and 1 theme are for Drupal 6, and are
development/alpha/beta quality code at the moment, but it might be
worth looking at them to see how they avoid doing full Drupal loads
but yet enable browsing the site:
* http://drupal.org/project/asynchronous
* http://drupal.org/project/page_renderer
* http://drupal.org/project/chrysalis
Good luck. This has been a long standing problem with Drupal.
--
..chris
On Wed, Jan 7, 2009 at 6:28 AM, Matej Svetlik <matej.svetlik at cetelem.sk> wrote:
> hello,
> thanks for all replies
>
> here is what i got so far:
>
>> The main problem is that Drupal 5 and earlier by design loaded ALL code on
>> every page load. In Drupal 6 we introduced split include files for page
>> callbacks, so most of those "foo.admin.inc" and "foo.pages.inc" files are
>> not,
>> in fact, loaded on every page request but only when needed. There are
>> similar
>> techniques that individual modules can implement if necessary for their
>> own
>> code, and some of the larger ones like Views and CCK do, but there's no
>> central mechanism for it.
>
> All my modules are split to many .inc files loaded only when needed. But
> drupal
> still includes all 67 .module files.
More information about the support
mailing list