Browse by Tags
Binary data and text file formats (JSON, XML) don’t tend get along. To be included in JSON or XML binary data has to be encode into a text friendly format, generally base64 , which creates overhead both in the time spent encoding/decoding binary, and the extra size of the text encoded data in the message. { "binary": "SGVsbG8gV29ybGQ=" } The Test In our test we’ll compare...
A lot of work around performance went into the latest release of Json.NET , with big improvements in both serializing and deserializing over the previous version. I can happily say that Json.NET is now faster than both the JavaScriptSerializer and the WCF DataContractJsonSerializer over all scenarios. Other .NET Serializers The latest performance improvements now puts Json.NET on the same level...
A new Json.NET release! As well as the new features below this release also adds documentation for common questions and I’ve spent some time having fun working hard on performance to make this the fastest version ever. Expect a post with sweet Excel graphs in the near future. Binary JSON (BSON) support Json.NET now supports reading and writing binary JSON (BSON). BSON is a standard for binary JSON...
Json.NET references a couple of assemblies that you wouldn’t expect for a JSON parser: System.Data.Linq (LINQ to SQL) System.Data.Entity (ADO.NET Entity Framework) Types from these assemblies are used to customize serialization behavior and make using Json.NET with them Just Work. While I always like things that Just Work, I’m not super happy about having dependencies on unrelated assemblies...
One of the common problems encountered when serializing .NET objects to JSON is that the JSON ends up containing a lot of unwanted properties and values. This can be especially important when returning JSON to the client. More JSON means more bandwidth and a slower website. To solve the issue of unwanted JSON Json.NET has a range of built in options to fine tune what gets written from a serialized...
More Posts
Next page »
