Whilst working my way through the conversation I was thinking from a user perspective who doesn't want to delve into the Agavi internals that you would want to refer to "Request" but since a Request can trigger off multiple actions it probably doesn't fit very well, but I like the idea of an "Agavi Processing Unit", so a Request may trigger off multiple Agavi Processing Units, which will consists of an Action, Validators, Views, Templates etc...
graeme. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
