Viewing profile — dweis

I believe that the reason for this limitation is that not all languages can represent open enums cleanly to gracefully handle unknown enums upon schema skew.

These are simply tradeoffs. For example, one can make very fast protobuf parsers/serializers if you prioritize that over the ergonomics of the generated code.

Yes, they are both varint encoded on the wire. Refer to https://developers.google.com/protocol-buffers/docs/encoding...

Minor nit, but not necessarily. For basically all values of SomeMessage, dec should fail to parse due to improperly encoded UTF8 data for field 2 (modulo some proto2 vs. proto3 and…

I don't think this is the case, or at least, I'd expect it to be a bug. Protocol Buffers should generally be non-destructive of the underlying data. That means even if it encounter…

How do you handle binary rollbacks and rollouts safely with an "everything is required" approach? Do you force binaries to roll out in a strict order with appropriate soak time at …

Hi there, I'm an actual author of Protocol Buffers :) I think Sandy's analysis would benefit from considering why Protocol Buffers behave the way they do rather than outright attac…

Thanks for pointing these out! This sort of archaeology is always interesting. I tend to have to do it for Protocol Buffers too to understand various design decisions.

Disclaimer: I have written and designed many parts of the Protocol Buffer libraries. https://tools.ietf.org/html/rfc1832.html#section-6 has a good encoding example of XDR. Contrast…

We use LevelDB.

Yes.

CMU's 15-440 Distributed Systems course did this over a year ago. See http://www.cs.cmu.edu/~dga/15-440/F12/ The professor, David Andersen, catalogued his experience on Google Plus…

This already existed for NYC: http://moredrunk.com