By controller plugins you mean, like a front controller and intercepting filters - or do you mean each controller has additional pre and post
action execution plugins.
I have use a pre-filter plugin to achieve basic authentication before, thus avoiding using a base controller to perform the checks and possible security hole introduced by failing to derive a controller from the proper superclass.
or one that maps request parameters to arguments of the action method.
My framework only supports system wide intercepting filters (pre and post). They are executed before and after each action invocation. So parsing a URI and initialing the request object with NVP, at this point, wouldn`t make much sense, at least it could be done more effectively in other places, in my setup anyways.
In any case, I think I understand what you mean by plugin architecture now, fairly standard with most MVC frameworks.
Just slightly different implementations.
Now I am actually curious though, how does a controller support pre and post plugins, in addition to the system wide intercepting filters -- do you derive from a base controller which provides this additional functionality. I have though about doing something like that in times past but could never think of a scenario where the problems are not better solved else where.
Cheers,
Alex