Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple architectures for any binary stream object. #39

Open
GoogleCodeExporter opened this issue May 21, 2015 · 0 comments
Open

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Create a binary stream in a 32 bit architecture machine using some types 
that depend on it (e.g. size_t.)
2. Send that stream to a 64 bit machine and attempt to read it.
3. Exceptions will be raised because of unsufficient stream size. Actually, the 
whole stream can't be read due to the fact that the 64 bit architecture is 
expecting 64 bit size_t data, etc.

We need to have serialized objects be able to be read from machines with other 
architectures than the one that serialized the object.


Original issue reported on code.google.com by billybiset on 30 Aug 2011 at 2:54

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant