[Tickets #11388] Application's API configuration can not be dynamically altered

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11388
------------------------------------------------------------------------------
  Ticket             | 11388
  Created By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Application's API configuration can not be dynamically
                     | altered
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz, Horde Developers
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-08-30 16:29) wrote:

Currently, we cache all API details.  This cache creation prevents  
dynamically altering the API object itself though (e.g. you can't  
dynamically disable API calls or add API links in __construct()).

We need to rethink/refactor API caching.  One option would be to cache  
the API objects themselves.  However, this would either 1) require the  
autoloader to be properly configured for ALL applications before  
unserializing or 2) adding autoloading code to the API object itself.   
Neither is desirable.

Instead, caching of the API may not be viable and we should remove it  
and load an application's API object on-demand.  Additionally, we  
should make the object's properties (disabled, links, noPerms)  
protected so that they have to be routed through the object's __get()  
method - then an object can override the __get() method as needed to  
add/disable elements.

This is blocking on Horde 5.0.