Skip to main content

Memento Pattern

Command Pattern 


Gamma Categorization: Behavioral Design Pattern
Summary: Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.

Sample Code

Problem: We want to apply several commands on the digital camera.

Code

public class DigitalCameraFirmware
{
    public string Name { get; set; }
    public byte[] Data { get; set; }

    public Memento SaveMemento()
    {
        return new Memento(Name, Data);
    }

    public void RestoreMemento(Memento memento)
    {
        this.Name = memento.Name;
        this.Data = memento.Data;
    }
}

public class Memento
{
    public string Name { get; private set; }
    public byte[] Data { get; private set; }

    public Memento(string name, byte[] data)
    {
        this.Name = name;
        this.Data = data;
    }
}

public class FirmwareMemory
{
    private Memento _memento;

    public Memento Memento
    {
        set { _memento = value; }
        get { return _memento; }
    }
}

Usage

var cameraFirmware = new DigitalCameraFirmware { Name = "v1.0", Data = new byte[1024] };

System.Console.WriteLine($"Current firmware version: {cameraFirmware.Name}");

FirmwareMemory memory = new FirmwareMemory();
memory.Memento = cameraFirmware.SaveMemento();

cameraFirmware.Name = "v2.0";
cameraFirmware.Data = new byte[1024];

System.Console.WriteLine($"Current firmware version: {cameraFirmware.Name}");

// something fails with the new firmware, so we want to restore the previous one
cameraFirmware.RestoreMemento(memory.Memento);

System.Console.WriteLine($"Current firmware version: {cameraFirmware.Name}");

Output

Current firmware version: v1.0
Current firmware version: v2.0
Current firmware version: v1.0

Comments

Popular posts from this blog

Software Development

Software Development Agile Agile is an insurance policy for market changes. By designing your solution according to this methodology, your project remains flexible and is always ready for change. It is always better to correct the mistake early in the process. With this method, you keep your finger on the pulse of a dynamic market and changing user expectations. As a result, you can continuously adapt, change your strategy, and create a product that will be in demand by the target audience, even if preferences have changed during the development process. DevOps DevOps is one more way to optimize the development budget of your application. A key DevOps approach is that this practice and its culture allow team members to better interact with each other and the customer. The software development team and those responsible for the operation of the application share responsibilities clearly, and it helps you avoid shifting responsibilities from one team member to another. DevOps involves th...

XML Webservice (ASMX) - SOAP Request and Response Invocation logging

You are an integration developer. Eventualy you came into the state where there is nothing else you can debug, and you have to check which SOAP request it is built on the request, and which SOAP response you are getting from the server. C# XML Webservice (ASMX) - SOAP Request and Response Invocation logging In the legaccy .NET framework System.Web.Services , this means using soapExtensions to help you intersept the interaction with the webservice. This is done like so:  public class TraceExtension : SoapExtension     {         Stream oldStream;         Stream newStream;         string filename;         // Save the Stream representing the SOAP request or SOAP response into          // a local memory buffer.          public override Stream ChainStream(Stream stream)         {           ...

SOLID (3/5) - Liskov substitution principle

  SOLID (3/5) - Liskov substitution principle Substitutability is a principle in object-oriented programming stating that, in a computer program, if S is a subtype of T, then objects of type T may be replaced with objects of type S (i.e., an object of type T may be substituted with any object of a subtype S) without altering any of the desirable properties of the program (correctness, task performed, etc.). More formally, the Liskov substitution principle (LSP) is a particular definition of a subtyping relation, called (strong) behavioral subtyping. It is a semantic rather than merely syntactic relation, because it intends to guarantee semantic interoperability of types in a hierarchy, object types in particular. using   System ; namespace   Liskov {      public   class   Rectangle     {          //public int Width { get; set; }   ...