Originally posted by peter, pan:
I mean do you use a single servlet to handle all form
actions(on end) or you use one servlet for each form
action(the other end)?
The most powerful approach IMHO is to have a single servlet (the controller) to handle actions. The servlet would dispatch the actions to command objects that implement the actual action. The whole thing is preferably controlled from a configuration file which lists, for each action/page combination, the commands to execute.
Controller and commands should all be stateless, so that they can be shared between all server threads. State belongs in the session and request objects.
Are there any performance issues etc.
that should be considered when designing?
Where do you want to start?
- Peter