--
You received this message because you are subscribed to the Google Groups "java-serialization-benchmarking" group.
To post to this group, send email to java-serializat...@googlegroups.com.
To unsubscribe from this group, send email to java-serialization-be...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/java-serialization-benchmarking?hl=en.
Had been fork on GitHub.:
https://github.com/szujobs/fastjson/tree/master/fastjson
On 8月7日, 上午3时20分, Eishay Smith <eis...@gmail.com> wrote:
> Would you like to fork the project on GitHub, add the fastjson code so we
> can pull it in?
>
>
I actually updated fastjson jar to latest, and optimized usage to bind
straight from byte array.
So I assume all that is needed is to re-run tests -- fastjson seems to
produce rather good numbers, possibly becoming the fast json
databinder tested.
-+ Tatu +-
Yes, I noticed that, very clever! And good thing is it works even if
order varies (or fields are missing), so that it is an optimization
and not requirement. And this definitely produces high throughput
numbers.
-+ Tatu +-
Fields for Wobly in ToolBehavior page should be:
Language-Neutral: no (java only)
Data Structure: annotate
Serialization: auto
Formats: binary
It is also backward and forward compatible.
Thanks,
ikabiljo