I am interested in using boost serialization for a project I am currently working on, but two requirements are hurting me.&nbsp; First, the archives have to be portable.&nbsp; Second, it&#39;s critical to keep the message size under a certain threshold which the text archives blow through.<br>
<br>So I am wondering if I can somehow get away with using a binary archive, even though my choices seem to be a non-portable version, or a unsanctioned tested version.<br><br>Oh, and I am pretty much stuck using Boost 1.32.<br>
<br>So, basically, I am wondering:<br><br>1.&nbsp; How non-portable is the non-portable archive?&nbsp; While this is a mixed windows/linux environment, all the computers are running as x86 or x86_64, so the endian is the same and word boundary restrictions are mostly the same.&nbsp; Unfortunately, the mapping of data types might not be the same.&nbsp; Is there a simple way to test this if the answer is &quot;maybe&quot;?<br>
<br>2.&nbsp; How stable is the portable archive?&nbsp; Reading through the release notes for 1.37 it seems like that the code is solid, except for encoding doubles, which would not be a problem.&nbsp; Of course, I am being forced to use 1.32, which might be much more unstable . . .<br>
<br>Thanks in advance for any replies.<br>