[.net] Deserialization problem

Started by
10 comments, last by Nypyren 15 years, 1 month ago
I actually wrote up a whole set of journals on doing essentially a custom serializer for your data. The final result is a bit buggy in some cases and not complete, but the concepts are all there. I wouldn't necessarily recommend it due to certain complications that can arise when dealing with versioning that are non-trivial to solve

In time the project grows, the ignorance of its devs it shows, with many a convoluted function, it plunges into deep compunction, the price of failure is high, Washu's mirth is nigh.

Advertisement
For network serialization, you can ignore version issues by requiring that all clients use the same executable. I didn't bother writing any versioning support into my system.

In my game, I used the custom serializer for network transfers, but used the heavyweight BinaryFormatter (with versioning info) for saved games. This meant I had to decorate some classes with a lot more serialization attributes than usual, but it worked well.

This topic is closed to new replies.

Advertisement