Hello everyone, last week i posted an issue that offers a very little patch that adds an interface for Zend_Controller_Action and changes the requirements of the Standard Dispatcher to this interface only (instead of the abstract action controller).
http://framework.zend.com/issues/browse/ZF-4385 (patch attached to it) I'd like some feedback if someone has Use-Cases for this issue (other then the ones i will specifiy later) or sees potential dangerous problems occuring to existing applications with this change. The interface (Zend_Controller_Action_Interface) will have only two required methods, the constructor accepting request, response and parameters, and the dispatch($action) method, since those are the only two methods used linking standard dispatcher and action controller. The current Zend_Controller_Action will of course implement this interface. Use-Cases and problem solvers: * Zend_Controller_Action has some final methods and lots of public methods. Some enviroments/projects might want to change certain behaviour of the controller without being able to do it currently. * Applications that run as webservice only, but need MVC facilities for central authentication, caching or other purposes through the front controller and plugin archtiecture. One could implement custom Action controllers that delegate all actions through SOAP, XMLRPC, (soon) AMF, JSON or Rest server objects. * Custom Controllers could be programmed that reduce the overhead of the current action controller in high performance setups without the need of overriding much of the current action controller but starting fresh. feedback for this issue is really appreciated (in the list or the issue itsself). Benjamin
