
???? ?????? wrote:
Hi
We are using boost serialization our product which was 32bit only till now. Now we have started building it on 64bit as well. On finding that boost::binary_archive is not platform independent, we seem to have 2 options:
1. Use text_archive - (but are worried about performance since the serialized data is approx 500MB even after gzip compression)
2. Use the eos portable archive - (but it is updated only till boost 1.49. We are using 1.53)
So my questions are:
1. One (and only one) of our archives created by our 32 bit executable is successfully read in by the 64 bit executable while the rest throw exception on reading the archive signature. If the platform is encoded in the signature, why is that one archive being read in successfully.
I couldn't say - maybe you just got lucky.
2. Which of the above two approaches would be better
If performance is an issue, I would try them both. It shouldn't be too tough to run a test.
and why.
Hmmm - It's hard for me to know which would be better. Note that the portable binary archive doesn't support floating point values
Thanks in advance.
Yours Sincerely Ashish Varman