The current autoload mechanism has the following disadvantages:

• autoload array for extensions needs to be regenerated each time you enable/disable an extension, which is too slow
• this concept is also not very understandable for non-technical users and should be more hidden from them, they should not be concerned about it when enabling/disabling extensions
• there's only one extensions autoload array, and not per site access

Suggestions to solve the issues:

• each extension needs to provide a file with its autoload array itself
• per site access, when enabling/disabling extensions, the autoload arrays coming from the different extensions are merged and put into one site access specific autoload cache file
• the ezpgenerateautoload script needs to be adjusted, so it accepts an extension name as command line argument and generates the autoload array for the specific extension then and puts it in a file inside this extension