> -----Original Message-----
> From: Jordan Thomas [mailto:[EMAIL PROTECTED]]
> What is the best way to design my application? Is it better to
> a) Put all my actions for a particluar area (i.e. creating,
> editing and
> deleting user accounts) in one Action class
>
> or
>
> b) Use a seperate action class for every action in my application
>
> or
>
> c) Put all of the actions for a particular workflow in a single Action
> class.
(b) in general is the best choice. Actions are basically like event
handlers in a GUI.
The drawback to (b) of course is that you:
* have a lot of classes
* have a lot of people potentially stepping on each other to add mappings
to the configuration file
Occasionally, when (b) is really, really overkill I'll use (c), but I
usually regret it later.
Just one man's opinion.
Cheers,
Laird
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
