On 7/25/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > I actually do not use any form of DispatchAction most of the time... very > rarely will I use anything along those lines. I find it to break the idea > of separating responsibilities. I prefer to see a well-named Action for > each actual action that can be invoked from a page. Whatever the > relationship is, I prefer this. I have some Actions that aren't tied to a > particular page at all, some that are very much page-specific, etc. Even > when they are only a few lines of code and bloat is not an issue if they > are all in the same class, I find it better architecturally for them to be > separate. Many people feel differently of course, but that's my > perspective on it.
DispatchAction allows you to have one mapping for a related set of operations. Therefore, you can call different operations for one object using the same web address, which is impossible using separate actions unless you use filter or something like mod_rewrite. Having same address is important to prevent browser history from growing, thus effectively disabling Back button. This makes application more robust and user experience closer to desktop application. You just might have not thought about that. Or, conversely, you stronlgly believe that each page change must be recorded in browser history, even if it is a series of login attempts, just because "browsers are supposed to do so" ;) Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
