Yes - you could use a different serialization format. The built-in serialization format is rich, but has downsides too - it's quite verbose compared with some other custom formats.
Yes - you could use a different serialization format. The built-in serialization format is rich, but has downsides too - it's quite verbose compared with some other custom formats. The format I'm most familiar with is Protocol Buffers, which is an efficient and portable binary format from Google.It does, however, require you to design the types that you want to serialize in a different way.
There are always pros and cons :) There are other binary serialization formats too, such as Thrift. You may want to stick to the built-in serialization, but it's worth knowing that other options are available. Before you go too far, however, you should determine what you care about and how much you actually need to worry about the performance anyway.
You could waste a lot of time investigating options when what you've got may be fine as it is :).
1 "You may want to stick to the built-in serialization": just for completeness - my constant argument about the built-in binary serializer (BinaryFormatter) is about brittleness, in particular versioning and implementation details. It does, however, have the convenience of being the simplest to get working. – Marc Gravell?
Nov 13 '09 at 22:05 1 "It does, however, require you to design the types that you want to serialize in a different way. " - it depends on which implementation you use... ;-p – Marc Gravell? Nov 13 '09 at 22:09.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.