When do we write a new Controller in Asp.net MVC? [duplicate]

Possible Duplicate:

When should I create new Controller class in Asp.net MVC (Design Question)?

I'm relatively new to ASP.net MVC and I was looking into the code of some app开发者_Python百科lication. I haven't given much of a thought for it earlier but when do we require a new controller? Are there any best practices regarding this?

This is probably a duplicate question - When should I create new Controller class in Asp.net MVC (Design Question)?...

...but, common practice is a new controller per resource, so for example, one for management of users, one for management of bookings etc. Then on each controller you'll have actions for add, modify, delete.