The Logstash configuration file is a custom format developed by the Logstash folks using Treetop. The grammar itself is described in the source file grammar.treetop and compiled using Treetop into the custom grammar.rb parser. That parser is then used by the pipeline.rb file in order to set up the pipeline from the Logstash configuration. If … Read more
Using gob and base64 could solve the problem, for example: import ( “encoding/base64” “encoding/gob” “bytes” ) type SX map[string]interface{} // go binary encoder func ToGOB64(m SX) string { b := bytes.Buffer{} e := gob.NewEncoder(&b) err := e.Encode(m) if err != nil { fmt.Println(`failed gob Encode`, err) } return base64.StdEncoding.EncodeToString(b.Bytes()) } // go binary decoder func … Read more
You used –decode_raw correctly, but your input does not seem to be a protobuf. For –decode, you need to specify the type name, like: protoc –decode header my.proto < b.bin However, if –decode_raw reports a parse error than –decode will too. It would seem that the bytes you extracted via gdb are not a valid … Read more
I’ve found the solution by myself, to add a custom field after the serialization has been done we’ve to create a listener class like this: <?php namespace Acme\DemoBundle\Listener; use JMS\DiExtraBundle\Annotation\Service; use JMS\DiExtraBundle\Annotation\Tag; use JMS\DiExtraBundle\Annotation\Inject; use JMS\DiExtraBundle\Annotation\InjectParams; use Symfony\Component\HttpKernel\Event\PostResponseEvent; use Acme\DemoBundle\Entity\Team; use JMS\Serializer\Handler\SubscribingHandlerInterface; use JMS\Serializer\EventDispatcher\EventSubscriberInterface; use JMS\Serializer\EventDispatcher\PreSerializeEvent; use JMS\Serializer\EventDispatcher\ObjectEvent; use JMS\Serializer\GraphNavigator; use JMS\Serializer\JsonSerializationVisitor; /** * Add … Read more
You can add a custom serializer to a single attribute like this: public class Comment { public string Author { get; set; } [JsonConverter(typeof(NiceDateConverter))] public DateTime Date { get; set; } public string Text { get; set; } } public class NiceDateConverter : JsonConverter { public override void WriteJson(JsonWriter writer, object value, JsonSerializer serializer) { … Read more
Technically on the low-level, your serialized object will also end up as a stream of bytes on your cable or your filesystem… So you can also think of it as a standardized and already available way of converting your objects to a stream of bytes. Storing/transferring object is a very common requirement, and it has … Read more
For future answer seekers, ProtoBuf now supports Maps natively: message MapMessage { map<string, string> MyMap = 1; }
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
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
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