Can controller be singleton?

Question

0.00/5 (No votes)

See more:

Guys,

I am implementing MVC pattern for my web site. I am thinking of implementing a controller as a singleton pattern. Anybody has any thoughts about how good/bad it is to have controller as a singleton class?

I think that controller should not anyway be responcible for maintaining user specific data. It should only act as a mediator between business layer and presenter. It should be the only place to access/update session data and if necessary it should perform validation.

All your thoughts about the advt and disadvts of having it as singleton are appreciated.

Thanks
Nyoti

Posted 17-Sep-10 1:31am

Nyoti Rukadikar

Updated 28-Nov-17 1:30am

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

TheyCallMeMrJames · Answer 1 · 2010-09-17T04:44:00

While I'm sure you could work around any of the limitations of this, given enough time, I don't see any benefit to this approach.

What platform are you on? What language? What version? Have you studied other MVC framework implementations?

Controllers (in the pattern) aren't directly responsible for maintaining user-specific data. Making it a singleton won't help that, nor can you prevent a user from making a direct connection to a database.

By nature of the stateless HTTP protocol, controllers will be created and destroyed endlessly. Whatever you do, make sure it can scale.

My $0.05.

Nyoti Rukadikar · Answer 2 · 2010-09-17T04:52:00

Thank you for your answer. I am working on ASP.NET C# 2.0.

The controller is responsible for creating business layer object and calling appropriate methods. As you mentioned correctly, it is not responsible for maintaining user specific data.

Now if 10000 users are accessing my site, then instead of creating 10000 objects of controller and intern 10000 objects of business layer, I thought it will be better if I create single instance of controller (ofcourse, containing business layer object as public property) and share it accross.

I have studied a bit about Spring MVC, ASP.NET MVC.

Can controller be singleton?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0