__autoload()instead of require_once * Using a global __autoload() function is not good practice for a framework because you can only have one __autoload function - I'm not in favor of it (ChuckHagenbuch). * Using it in Horde apps as opposed to the framework is an option, but still leaves us all of the framework requires. * http://php.net/spl-autoload-register is a potential solution. With PHP 5.1.x (or 5.2, or ...) as a minimum version requiring SPL should be okay. * Performance a consideration? http://pooteeweet.org/blog/538/* RemoveGlobals * ((Project/HordeSpaces)) * Require UTF-8 support * Require PHP 5.3+ and use the intl extension (http://us3.php.net/intl) * Remove confusing mess of hooks and other ways of muddling logins (especially with IMP), and replace them _all_ with the preauthenticate and postauthenticate hooks + appropriate examples for things like vhosting. * Clean up tobackend/frombackend hooks - either remove them, or name them better, or document when and where they need to be called. * Get rid of 'realms' (replace with ((Project/HordeSpaces)) where necessary). * Remove imp['uniquser'] ? * Horde4Config * Per-variable session locks? http://thwartedefforts.org/2006/11/11/race-conditions-with-ajax-and-php-sessions/ * Use 1 login screen for all apps? (i.e. Horde_Login:: library) * Use hash() instead of md5 or sha1 directly for speed (http://us.php.net/manual/en/function.hash.php) * Deal w/CSS namespace clashing issues in portals (see, e.g., http://bugs.horde.org/ticket/?id=5831). Prefix all css rule names with the application name (.horde-header)?