Skip to main content

Creational Design Patterns-Singleton Pattern


Singleton Pattern

The purpose of the Singleton pattern is to make sure that there is only one instance of a class and that there is a global access point to that object.
The pattern ensures that the class is instantiated only once and that all requests are directed to that one and only object.

The class needs to make the following modifications in order to implement the Singleton Pattern

  •  The constructor needs to be made private and add a private static constructor as well.
  •  A private static read-only object is required, that is internally instantiated using the private constructor.
  •  A public static property is required, that accesses the private object.


It is the public property  that is now visible to the caller.
All constructor requests for the class go to the property. The property accesses the private static object and
will instantiate it if it does not already exist.

Example:
 public  sealed class SingletonDemo
{
      private SingletonDemo()
      {
      }

    private static SingletonDemo _myobject = new SingletonDemo();
    public static SingletonDemo isInstatiated
    {
        get { return _myobject; }
    }
}
As soon as the class is instatiated, isInstatiated property is set be calling its private constructor.


Let’s call it to see how it works
protected void Page_Load(object sender, EventArgs e)
    {

        Response.Write("Simple Singleeton Demo");
        Response.Write("");
        if (SingletonDemo.isInstatiated != null)
        {
            Response.Write("Object initialized");
        }
     }


To further extend the demo, try to instatiate two objects for this class and see if they point to different references.

Although I assure you that it always creates just one instance, please try it yourself  to believe if I’m correct.

Hope this was helpful,

Till next time we connect…Happy Coding!!!

Comments

Post a Comment

Popular posts from this blog

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...
Post a Comment
Read more

Covariance and Contravariance-General Discussion

If you have just started the exploration of .Net Framework 4.0, two terms namely Covariance and Contravariance might have been heard. The concept that these terms encapsulate are used by most developer almost daily, however there has never been any botheration about the terminologies. Now, what actually these terms mean and how are these going to affect us as a developer, if we dive in to the details. The simple answer is it’s always good to know your tools before actually using them. Enough philosophy, let’s get to the business. Starting the discussion let me reiterate that in addition to Covariance and Contravariance, there is another terminology, Invariance. I’ll by start here by diving into the details of Invariance and then proceed further. Invariance: Invariance can be better understood by considering the types in .Net.>net has basically two type, value-types and reference-types. Value types (int, double etc) are invariant i.e. the types can’t be interchanged either ...
1 comment
Read more

WCF-REST Services-Part-I

What is REST? REST stands for Representational State Transfer. REST as described in MSDN, “is an architectural style that can be used to build software in which clients (user agents) can make requests of services (endpoints)”. REST is one way to implement a client-server architectural style. A service that uses the architectural style of REST is generally referred to as a RESTful service or endpoint. RESTful endpoint Building Blocks 1. Resources(What resources would the service Serve/Offer) 2. URI(Identifiers used to represent the resources) 3. HTTP Verbs (What parts of the uniform interface (HTTP verbs) are each URI going to support, like Get/Post etc.) I’ll develop a hypothetical system that will make use of these blocks in the next article, let us consider the theoretical aspects of the REST in this post. Why REST? As explained above, REST internally implements a Client/Server model that can be easily achieved by using SOAP with ASMX or WCF. Just for the discussion sake ...
Post a Comment
Read more