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

Tests & Experiments #41

Closed
grigorey opened this issue Jan 30, 2015 · 5 comments
Closed

Tests & Experiments #41

grigorey opened this issue Jan 30, 2015 · 5 comments

Comments

@grigorey
Copy link

Hi, I'll post my findings here :) By the way try run tests against http://fastjson.codeplex.com I will use it in my test :)

@rpgmaker
Copy link
Owner

I follow this test. https://github.com/amacal/Quality.Json
On Jan 30, 2015 5:35 AM, "Gregory S" notifications@github.com wrote:

Hi, I'll post my findings here :) By the way try run tests against
http://fastjson.codeplex.com I will use it in my test :)


Reply to this email directly or view it on GitHub
#41.

@grigorey
Copy link
Author

Sweet, thanks for the link!

@rpgmaker
Copy link
Owner

If you can help in making suggestions to improve performance overall to
make netjson faster than or as fast as binaries that would be great.
Netjson is already faster than all json (based on all the benchmark online)
that I have seen and tested and also beat messageshark and protobuf on some
use cases.
On Jan 30, 2015 8:23 AM, "Gregory S" notifications@github.com wrote:

Sweet, thanks for the link!


Reply to this email directly or view it on GitHub
#41 (comment).

@rpgmaker
Copy link
Owner

Closing this issue. Open a new issue when there are any changes to be made to netjson. Thanks

@grigorey
Copy link
Author

Cool!

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

No branches or pull requests

2 participants