What is a good way to serialize remote commands?

Question

I've been working into a small game just for learning. The intent of the game is that it is going to be online, but I have some trouble on how to serialize the commands sent from server to client. There is a lot of different commands that can be sent, and handling this manually is driving me insane. At the moment I'm using lots of 'ifs' to do this, but I hope there is a Design Pattern that helps. I would like to unpack the message in different kinds of objects so I could get them from some kind of queue and treat them efficiently... But I would like to do it partially or completely automatic.

Is there a good practice to solve this kind of problem? It would be good if it was efficient too.

Thanks in advance.

PS: Although this is a conceptual question, I'm using C++, so some specific solution would be fine too.

score 1 · Answer 1 · answered Jul 15 '13 at 03:34

1

There is a design pattern called "actors", which might be what you want. Features:

natual and simplified concurrency model.
could be used together with pattern matching over messages (eliminate "ifs").

Language 'scala' provides good support for this design pattern and perfectly meet your need. However, I don't know whether there is similar solution in C++.

answered Jul 15 '13 at 03:34

user1583862

11
2

Actor model is very easy to implement. Look how simple it may be at https://github.com/rfqu/CodeSamples/tree/master/src/simpleactor . It is written in java, but can be easily rewritten in C++. It requires an Executor, which is simply a thread pool, and https://www.google.com/search?q=thread+pool+c%2B%2B shows that there are many thread pool implementations in C++. – Alexei Kaigorodov Jul 19 '13 at 08:00

score 1 · Accepted Answer · edited May 23 '17 at 10:32

Try a Factory pattern. Something along these lines is a useful factory model.

Make a base class that provides methods for serialising and deserialising data from a stream, and register your derived types by name or some other identifier with the factory.

You can package up a command in a bundle with a header that tells the receiver what type to create. When you read a command, you ask the factory to create the correct type. Then returned type can then be called to deserialise its data.

Here, I'm assuming that some commands have extra data.

Once you have popped the command out of the queue for processing, you can call its 'Execute' method.

What is a good way to serialize remote commands?

2 Answers2