I just call them action methods, no matter what form they take. They can be S1's Action.execute(), a method that EventActionDispatcher calls, a Command implementation, a POJO method, whatever. They're all in response to <form action="/xyz">. Well, okay, so some of them are GET calls. But sticking to the term "action" or "action method" gives me consistency.
Hubert On 7/18/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
On 7/18/06, Ted Husted <[EMAIL PROTECTED]> wrote: > On 7/18/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > >Does anyone have better term for Action/Command? > > In other places, I refer to such things casually as "handlers". People > have often used this word on the list to distinguish between the > action mapping and the Action class (handler). What if I use dispatch-type action/command? How do I call methods that correspond to events? Presently I call them "event handlers" or "handler methods". Another choice is to keep "handlers" for methods as in "event handlers", and to call Action/Command collectively as... command, like Martin Fowler does [1] or like MSDN defines Front Controller pattern [2]. [1] http://www.martinfowler.com/eaaCatalog/frontController.html [2] http://msdn.microsoft.com/practices/apptype/webapps/default.aspx?pull=/library/en-us/dnpatterns/html/DesFrontController.asp Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
