Inheriting from generated C++ classes for adding Qt QString accessors. Problems expected?

2009-03-09 Thread bart van deenen
Hi all I'd like to add some Qt specific addditions to some generated gpb classes, but I note the warning on the first C++ page of the documentation: You should not create your own Foo subclasses. If you subclass this class and override a virtual method, the override may be ignored, as many

Swap() and RemoveLast() should be added to Reflection API

2009-03-09 Thread Scott Stafford
Hi - I noticed that the functionality for Swap() and RemoveLast() was not available to reflection. I needed them and tried to add them in a branch, and it seemed trivial enough (especially RemoveLast). Is there anything that I missed? Is there a reason that this is more complex than I can see

Re: Inheriting from generated C++ classes for adding Qt QString accessors. Problems expected?

2009-03-09 Thread Kenton Varda
If you are OK with the possibility that future versions of protocol buffers may break your code (probably in minor ways), then you can do whatever you want. If you aren't OK with that, then you should not subclass protocol buffer types. There are tons of ways that future changes to the

Any protocol buffers MIME types?

2009-03-09 Thread Marc Gravell
As part of ongoing work looking at RPC (over a range of transports), one thing that keeps cropping up is sending messages via a RESTful API over http[s] (so the method to invoke it part of the URI, with the message as the body); pretty trivial to do, but I wonder: is there any common MIME type

Re: Any protocol buffers MIME types?

2009-03-09 Thread Kenton Varda
We haven't defined a MIME type. Does it make sense to define a MIME type for protocol buffers in general, as opposed to MIME types for individual protocols? The latter makes more sense to me, since there's not much you can do with a protocol buffer without knowing its type. On Mon, Mar 9, 2009