[protobuf] why does int64, fixed64, uint64 serialise to string in JSON

Hi, As per this doc: https://developers.google.com/protocol-buffers/docs/proto3#json, int64, fixed64, uint64 are suppose to serialise to string in JSON. Are there any specific reasons for this choice? It is non standard and breaks a other JSON parsers and JS itself. -- You received this messa

[protobuf] why does uint64, fixed64 map to string when converted to JSON

Hi, I was looking at this document: https://developers.google.com/protocol-buffers/docs/proto3#json and noticed that int64, fixed64, uint64 are mapped to string when converting to JSON. Any specific reason why this is done? This deviation breaks a lot of other JSON parsers and any code in JS t

[protobuf] Re: why does uint64, fixed64 map to string when converted to JSON

Thanks a lot Jon. I have been dealing with JSON usually in the backend far more than with Javascript. On Tuesday, July 19, 2016 at 6:28:22 PM UTC+5:30, Jon Skeet wrote: > > On Monday, 18 July 2016 18:25:41 UTC+1, Shashwat Agarwal wrote: >> >> I was looking at this d

[protobuf] Missing sources and javadoc jars of Protobuf 3.0.0-beta3 in Maven Central

Hello, It will be great if someone can upload the javadocs and source jars of protobuf 3.0.0-beta3 (http://central.maven.org/maven2/com/google/protobuf/protobuf-java/3.0.0-beta-3/) TIA -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To uns