On 7/22/06, Ted Husted <[EMAIL PROTECTED]> wrote:
On 7/22/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> I really don't like calling action a handler. Well yes, it is a
> request handler, but I would like to reserve "handler" as in "event
> handler" for dispatch action methods. Also, ASP.NET and JSF uses
> "event handler" for code-behind class methods, so this way Struts
> terminology will be in sync.
From a s1/s2 perspective, actions are our events, and Action classes
correlate to how ASP.NET uses code-behinds and JSF uses backing beans.
IMHO, It's perfectly appropriate to refer to all of these notions as
"handlers".
How would you differentiate actions that process one "flavor" of
request (regular action) and actions that process several events
(dispatch actions)? What about something like "coarse-grained
handlers" and "fine-grained handles"? And which one is which?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
