Adapter pattern works as a bridge between two separate objects. It converts interface of a class into another interface which is required. Adapter pattern lets different classes work together that could not otherwise due to the different interface of each class.
Understanding Adapter pattern is not that difficult because it works same as we see an adapter in the real world. The simplest example is AC power adapter which we use for cell-phone, laptop chargers. Electricity at home socket is 220 volts (or 110 volts) but our cell phone needs 5-12 volts so we need an adapter which should convert the power to required range.
Adapter in Programming
Let's see a real world example for Adapter pattern. Information sharing system's team is working on a system which uses social networks sites to share the content. The team has designed an interface which is implemented by Facebook, Twitter, and Linkedin classes. The system is using this interface to switch between these sites and share the content. Developers have to spend a lot of time in implementing these network site's public APIs in these classes and make system bug free and tested.
Here is code implementation of the system.
public interface ISocialNetworks
{
bool Login(string username, string password);
bool Share(string content);
}
public class Facebook: ISocialNetworks
{
public bool Login(string username, string password)
{
//Login Using Facebook API
}
public bool Share(string content)
{
//Share Using Facebook API
}
}
public class Twitter: ISocialNetworks
{
public bool Login(string username, string password)
{
//Login Using Twitter API
}
public bool Share(string content)
{
//Share Using Twitter API
}
}
//similarly for Linkedin
Everything was working fine until client wanted Google+ also in the list and team know to implement the same interface you have to understand APIs and have to put a huge effort in implementations. But you found that Google+ has already developed a library so you downloaded that library and try to integrate into your system.
There is a little problem Google+ developers have implemented their own interface which is not compatible with our information sharing system. Here is the code:
public interface IGoogleSocialNetworks
{
bool Authenticate(string username, string password);
bool Post(string content);
}
public class GooglePlus: IGoogleSocialNetworks
{
public bool Authenticate(string username, string password)
{
//Login Using Google API
}
public bool Post(string content)
{
//Share Using Google API
}
}
Now here comes the adapter which will convert interface of Google+ library to the interface of desired system interface i.e, ISocialNetworks. Let's see its code implementation
public class GoogleNetworksAdapter: ISocialNetworks
{
GooglePlus GoogleLibrary;
public void GoogleNetworksAdapter (GooglePlus googleLibrary)
{
this.GoogleLibrary = googleLibrary;
}
public bool Login(string username, string password)
{
GoogleLibrary.Authenticate(username, password);
}
public bool Share(string content)
{
GoogleLibrary.Post(content);
}
}
Let see design diagram after implementing adapter pattern
Now since Google+ adapter has the same interface as our other Social Networks i.e, ISocialNetworks so it can be use in system easily. Here is how client uses the adapter:
- Client make a request to Adapter class (GoogleAdapter) for a method of target interface (ISocialNetworks) e.g, Login
- Adapter class translate that request to adapted object method (IGoogleSocialNetwoks) e,g, Authenticate and return response
- Client receive the response without realizing that Adapter converted its request to another form.
Here is the class diagram of Adapter Pattern
Adapter pattern uses other good practices of Object Oriented for example object composition in Adapter class to wrap adapted functionalities in target interface. Another advantage of using this object composition is that this adapter can be used with any child class that inherits this Adapted class.
No comments:
Post a Comment