Comments (0)

This article is written under ‘Quick and Short’ edition. In this article I will explain about verious Design Patterns.

Read more Quick and Short articles.

Design Pattern

Design patterns are recognized solutions to common problems defined originally by the Gang of Four programmers.

Design patterns are tried and tested solutions for recurring problems in a given context. So basically you have a problem context and the proposed solution for the same. Design patterns existed in some or other form right from the inception stage of software development. Let’s say if you want to implement a sorting algorithm the first thing comes to mind is bubble sort. So the problem is sorting and solution is bubble sort. Same holds true for design patterns.

The various patterns are commonly divided into several different groups depending on the nature of the design problem they intend to solve.

Creational Patterns

• Factory - This pattern is used to create concrete class instances without specifying the exact class type.
• Abstract Factory – This pattern is used to create concrete class instances without specifying the exact class type. The Abstract Factory Pattern provides a way to encapsulate a group of individual factories that have a common theme.
• Singleton - This pattern insures that only a single instance of a given object can exist.
• Builder – This pattern separate the construction of a complex object from its representation so that the same construction process can create different representations.
• Prototype:- A fully initialized instance to be copied or cloned

Structural Patterns

• Adapter – Convert the interface of a class into another interface clients expect. Adapter lets the classes work together that couldn’t otherwise because of incompatible interfaces
• Bridge – Decouples an abstraction from its implementation so that the two can vary independently.
• Composite – Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.
• Decorator – Allows an objects behavior to be altered at runtime.
• Facade – Used to provide a simpler interface into a more complicated portion of code.
• Proxy – Provides a Placeholder for another object to control access to it.

Behavioral Patterns

• Flyweight – A fine-grained instance used for efficient sharing.
• Chain of Responsibility – The chain of responsibility pattern is a way of communicating between objects.
• Command - Encapsulates a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.
• Iterator – Provides a way to sequentially access aggregate objects without exposing the structure of the aggregate.
• Mediator – The mediator pattern encapsulate the interaction between a set of objects.
• Memento – Allows you to save the state of an object externally from that object.
• Observer – Allows a single object to notify many dependent objects that its state has changed.
• State – Allows an object to change its behaviour when its internal state changes.
• Strategy – Allows multiple algorithms to be used interchangeably at runtime.
• Visitor – The visitor design pattern enables us to create new operations to be performed on an existing structure.
• Template Method -  Defines the skeleton of an algorithm then lets subclasses implement the behaviour that can vary.
• Interpreter - A way to include language elements in a program.

——————————————————————————————————————————————————————

Readers are requested to add comment, and add more information in case they want.

Read more Quick and Short articles.

Comments (0)

Any useful executable program involves either reading input, writing output, or both. Regardless of the source of the data being read or written, it can be treated abstractly as a sequence of bytes. .NET uses the System.IO.Stream class to represent this abstraction. Whether the data involves characters in a text file, TCP/IP network traffic, or something else entirely, chances are you will have access to it via a Stream. Since the class for working with file data (FileStream) and the class for working with network traffic (NetworkStream) both inherit from Stream, you can easily write code that processes the data independent of its origins. Here’s a method for printing out some bytes from a Stream to the console:

Copy Code public static void PrintBytes(Stream s)
{
    int b;
    while((b = fs.ReadByte()) >= 0)
    {
        Console.Write(b + ” “);
    }
}

  Read more »