I'm using boost.serialization for part of our messaging solution. Now here comes a problem: we want to communicate between 32bit and 64bit, is there a chance that using "text archive" would solve the problem ? jinqiang Zhang
Jinqiang Zhang wrote:
I'm using boost.serialization for part of our messaging solution. Now here comes a problem: we want to communicate between 32bit and 64bit, is there a chance that using "text archive" would solve the problem ?
It should - but there might be some caviats. Suppose you generated an integer on your 64 bit machine longer than 32 bits. That is larger than 2^32 (~4,000,000,000. There is no way that the 32 bit machine can prepresent it so this wouldn't work. This isn't a problem with the library but an inherent limitation representing 64 bit integers on a 32 bit machine. Other than this, it shold be fine. Robert Ramey
On 05/09/2011 08:38, Robert Ramey wrote:
Jinqiang Zhang wrote:
I'm using boost.serialization for part of our messaging solution. Now here comes a problem: we want to communicate between 32bit and 64bit, is there a chance that using "text archive" would solve the problem ? It should - but there might be some caviats.
Suppose you generated an integer on your 64 bit machine longer than 32 bits. That is larger than 2^32 (~4,000,000,000. There is no way that the 32 bit machine can prepresent it so this wouldn't work. This isn't a problem with the library but an inherent limitation representing 64 bit integers on a 32 bit machine.
Other than this, it shold be fine.
Robert Ramey _______________________________________________ Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Hi Jinqiang,
I believe there is also the eos portable binary archive, see eos_portable_archive.zip <https://github.com/boost-vault/serialization/blob/master/eos_portable_archive.zip> in https://github.com/boost-vault/serialization. <https://github.com/boost-vault/serialization> Cheers, Jon
Many thanks Robert & Jon. Jon, what's 'boost-vault' ? is it something going into boost eventually? If it's not case, probably I can't use it, since maintaining 3rd party would be harder for us. I would try "text archive" first. cheers, Jinqiang On Mon, Sep 5, 2011 at 6:36 PM, Jon Payne <jpayne@hgl-dynamics.com> wrote:
On 05/09/2011 08:38, Robert Ramey wrote:
Jinqiang Zhang wrote:
I'm using boost.serialization for part of our messaging solution. Now here comes a problem: we want to communicate between 32bit and 64bit, is there a chance that using "text archive" would solve the problem ?
It should - but there might be some caviats.
Suppose you generated an integer on your 64 bit machine longer than 32 bits. That is larger than 2^32 (~4,000,000,000. There is no way that the 32 bit machine can prepresent it so this wouldn't work. This isn't a problem with the library but an inherent limitation representing 64 bit integers on a 32 bit machine.
Other than this, it shold be fine.
Robert Ramey ______________________________**_________________ Unsubscribe& other changes: http://lists.boost.org/** mailman/listinfo.cgi/boost<http://lists.boost.org/mailman/listinfo.cgi/boost>
Hi Jinqiang,
I believe there is also the eos portable binary archive, see eos_portable_archive.zip <https://github.com/boost-** vault/serialization/blob/**master/eos_portable_archive.**zip<https://github.com/boost-vault/serialization/blob/master/eos_portable_archive.zip>> in https://github.com/boost-**vault/serialization<https://github.com/boost-vault/serialization>. <https://github.com/boost-**vault/serialization<https://github.com/boost-vault/serialization>
Cheers, Jon
______________________________**_________________ Unsubscribe & other changes: http://lists.boost.org/** mailman/listinfo.cgi/boost<http://lists.boost.org/mailman/listinfo.cgi/boost>
participants (3)
-
Jinqiang Zhang -
Jon Payne -
Robert Ramey