By default you don’t need to use neither [Serializable] nor [DataContract] to work with Web API. Just leave your model as is, and Web API would serialize all the public properties for you. Only if you want to have more control about what’s included, you then decorate your class with [DataContract] and the properties to … Read more
They both offer many of the same features; however, there are some differences: Thrift supports ‘exceptions’ Protocol Buffers have much better documentation/examples Thrift has a builtin Set type Protocol Buffers allow “extensions” – you can extend an external proto to add extra fields, while still allowing external code to operate on the values. There is … Read more
If you zip a file named a.txt containing the text “hello” (which is 5 characters), the result zip will be around 115 bytes. Does this mean the zip format is not efficient to compress text files? Certainly not. There is an overhead. If the file contains “hello” a hundred times (500 bytes), zipping it will … Read more
I believe there may be some gremlins in that previous answer – will log as an issue :/ There are other possible routes to achieve this type of complex serializable object navigation still using Json and overriding parts of the framework, but actually I think that it might be better to just use your own … Read more
While matt b’s answer will work, you can also use .serializeArray() to get an array from the form data, modify it, and use jQuery.param() to convert it to a url-encoded form. This way, jQuery handles the serialisation of your extra data for you. var data = $(this).serializeArray(); // convert form to array data.push({name: “NonFormValue”, value: … Read more
You can use the untagged attribute which will produce the desired output. You won’t need to implement Serialize yourself with this: #[derive(Debug, Serialize)] #[serde(untagged)] enum TValue<‘a> { String(&’a str), Int(&’a i32), } If you wanted to implement Serialize yourself, I believe you want to skip your variant so you should not use serialize_newtype_variant() as it … Read more
Marshaling and serialization are loosely synonymous in the context of remote procedure call, but semantically different as a matter of intent. In particular, marshaling is about getting parameters from here to there, while serialization is about copying structured data to or from a primitive form such as a byte stream. In this sense, serialization is … Read more
This has been implemented by dtolnay. The concept is quite clever ans is explained in the README: How does it work? We use the inventory crate to produce a registry of impls of your trait, which is built on the ctor crate to hook up initialization functions that insert into the registry. The first Box<dyn … Read more
Done myself: test.proto enum MyEnum { Default = 0; Variant1 = 1; Variant100 = 100; } message Test { required string f1 = 1; required int64 f2 = 2; repeated uint64 fa = 3; repeated int32 fb = 4; repeated int32 fc = 5 [packed = true]; repeated Pair pairs = 6; optional bytes bbbb … Read more
I’ve already figured out my problem and found the solution. OData uses separate media type formatters, inherited from ODataMediaTypeFormatter. Also OData uses different formatters for serialization and deserialization. For replacing this behavior we have to implement descendants of ODataDeserializerProvider and/or ODataSerializerProvider classes and add those classes to the HttpConfiguration.Formatters collections by var odataFormatters = ODataMediaTypeFormatters … Read more