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
[Android] BigInteger #55
Comments
:) that's not spamming, its actually helpful. man i did not imagine so many issues with android .. Was this fst 2.22 ? |
Yes. |
The following custom serializer worked for me:
|
Cool ! I thought about registering custom serializers for BigDecimal and BigInteger by default as the JDK emulation for putFields stuff is slowish. |
Evaluated the issue and found its impossible for fast-ser to catch this by "emulating" JDK except by adding a huge overhead to all classes using JDK-ser methods (e.g. readObject). So only solution is adding your custom serializer to default init of FSTConfiguration. Watch out for / avoid double custom serializer registration as you update to 2.23 :-). I really hope there won't be too many classes having similar issues. However even adding a handful of custom serializers is advantageous to dropping performance in half (+much larger size on wire). Fixed with 2.23 (custom ser addition) |
Yes, your argumentation makes sense and I see the point. There's no need to decrease overall performance just to support some crappy Android classes. Thanks for adding the custom serializer to the library. The 'registerObject' line was missing in
|
The registerObject ensures the object is only written once in case its Thanks for your report+fix and keep the bugs coming :-) 2015-02-08 21:11 GMT+01:00 Nico Rutishauser notifications@github.com:
|
Sorry for spamming you with nasty exceptions of Android incompatibilities. Here's the next one:
As soon as I've more time, I'll look deeper into the FST code to probably be able to fix them myself.
The text was updated successfully, but these errors were encountered: