[commits] [Wiki] changed: Project/H6TODO

[Michael Slusarz]

slusarz  Tue, 15 Jul 2014 19:53:23 +0000

Modified page: http://wiki.horde.org/Project/H6TODO
New Revision:  8
Change log:  AJAX framework improvements

@@ -11,9 +11,9 @@
    * All Horde code/libraries should use $logged parameter of Horde_Exception
    * Remove Horde_Exception_Wrapped
    * (Discuss) Provide separate error message for admins vs. error  
message meant for end user display
  * Remove External session handler from horde/conf.php
-  * This can be accomplished by creating a SessionHandler class and  
passing in this classname to 'type'.
+  * This can be accomplished by creating a !SessionHandler class and  
passing in this classname to 'type'.
  * Horde_Translation
    * Vastly simplify framework library implementation by using late  
static binding - should only need to declare the path to the base of  
the application in a member variable.

  ++ To Discuss
@@ -22,8 +22,11 @@
    * Have config file be a class that extends/implements a base Horde  
class/interface.  All hooks can be defined without having to comment  
them out - active hooks would then be defined in a public variable  
config array.  Another idea: hooks live in a separate subfolder ...  
one hook per file.  hooks.php has name of class to load.
  * Centralized GC
    *  Want to add a global Horde GC system. Libraries implement GC  
class, and when triggered we don't immediately do GC but instead send  
GC requests to a queue. Then we either do ALL GC requests on a random  
access (i.e. logout access; this doesn't require any admin setup) or  
admin would have option to run cron process to periodically handle GC  
queue.
  * Websockets version of AJAX endpoint
+* AJAX framework improvements
+  * Remove "Handlers". Replace with a separate file/object for each  
action.  Allows more granular support re: permissions/read-only
+  * Provide a way (callback?) to alter the JSON output at send-time
  * Log improvements
    * Ability to queue log entries (configurable), for logging after request.
    * Also... right now, we need to fully process log entry before we  
know if we are going to accept, since log level checking happens at  
the lowest levels of logging chain. Need to move this up in chain so  
that we can exit out of log code earlier if we know that we don't want  
to process.
  * Application API access