|
-
August 3rd, 2008, 07:03 AM
#1
Protocol implementation advice
Hello,
I am currently writing an application that is using an already existing protocol to send/receive data. The protocol is text based, there are like 20 different commands that can have multiple arguments.
Now I was wondering what is the best way to implement this in C#. Currently I have it all working with a single Message class, where I set the arguments using a ListDictionary and then build a string to send. However, I've seen some protocol implementations, that use a different class for every different message in the protocol. It seems attractive, but doesn't it add some overhead to the application? The messages won't be sent more often than every 2 seconds.
I'd like to ask what's you opinion on this matter? What are the advantages and disadvantages between these two designs?
Thanks in advance.
Using .NET 2.0 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|