Harshana Dias wrote:
Jeanne Boyarsky wrote: Your logic should be in other classes you delegate to. And there would be one of those per action.
Those are the model classed in MVC architecture know.
No, that's not what's she's talking about. Perhaps this article can help.
Piyush Mangal wrote:It is fine to have one controller for both delete and update action as long as they can be functionally grouped. Even frameworks like Struts and Spring MVC had DispatchAction and MultiActionController for the same usecase.
That's true. The original poster didn't sound that far down in design so I answered differently.