Communication pattern

Question

0.00/5 (No votes)

See more:

Hi,

I have to create a communication protocol implementation.
For now, this protocol is based on RS232, but in the future we want to add a TCP/IP implementation of this protocol.

Now I'm looking for the best way of implementing this so adding new communication media is easy to integrate.

Are there some design patterns that are usefull? I have looked to the Adapter pattern and think this is an option but, maybe you have an better idea or article to refer to.

Regards,
Jerry

Posted 7-Feb-10 21:05pm

Jerry van Kranenburg

Add a Solution

3 solutions

Solution 1

I am not sure if I understood you well, but you mixed things up here, you are talking about a communication protocol like TCP/IP or UDP and in the same time you want to implement it with a design pattern !?!! I think your worries should be bigger than that.

Posted 7-Feb-10 21:17pm

Samer Aburabie

Solution 2

No, we have an communication protocol to talk with our machines. It's working over a RS232 line right now.

But, we have to refactor this application and want to have the posibilitie to add another communication medium eg TCP/IP. But ofcource, we do not want to have the knowledge about Serial line or TCP/IP commands in our application.

Only the "Communication Layer" must be infacted when we add another communication media.

So that's why I want to find the best way of doing this. With a good design it must be possible :-)

Posted 7-Feb-10 21:25pm

Jerry van Kranenburg

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)

Nicholas Butler · Accepted Answer · 2010-02-07T23:13:00

I would encapsulate the higher level functions in an interface with a method SendMessage and an event MessageReceived. You can then write concrete implementations for whatever communication layers you need.

You can then write a class with methods specific to your protocol, like GetWidgetCount, that use the interface. This is like the State pattern. To use a particular concrete implementation, you would just have to change the line:

C#

ICommunicate communicator = new TcpIpCommunicator();

Nick