Looking over the [Wave protocol spec][1], it appears that they're
using XMPP which has no entry in the /etc/mime.types on my system, but
does have application/xmpp+xml mentioned in RFC3293. Which leaves us
with absolutely nothing in terms of a MIME type for protocol buffers.
One thing to note is
Nope, there hasn't been any off-list discussion.
Personally I have no opinion on the matter since it doesn't affect anything
that I do with protocol buffers. However, the Google Wave people -- who are
developing an open-source protocol that will use protocol buffers -- seem to
care about this and
Even if the stream of bytes has no semantic meaning without
the .proto, its format is still protobuf binary, so the MIME type
makes some sense even if it is not sufficient.
Putting a ref to the appropriate .proto in the HTTP headers REST-style
seems sensible - loosely similar to declaring a
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
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
