For the curious, the process of getting a new IANA content type is covered
I like Wolfgang and AVRO-488's suggestion of application/avro+binary and
application/avro+json, but I'm concerned about the overhead of trying to
get Avro through an IETF RFC. (ref sec 3.1)
One alternative we could try would be to add a vendor tree option (ref sec
3.2) for avro as an apache project, eg
I'm not entirely sure what kind of authority needs to be vested with
whoever shows up as a poc for the registration, presumably a PMC for the
project would be suitable?
It would probably be worth including in the type string if something is an
Object Container or a Protocol.
On Mon, Oct 22, 2012 at 6:08 PM, Wolfgang Hoschek
> Forwarding this question to dev list per Sean's suggestion.
> Begin forwarded message:
> > From: Sean Busbey <[EMAIL PROTECTED]>
> > Subject: Re: Avro mime type
> > Date: October 22, 2012 2:58:10 PM PDT
> > To: [EMAIL PROTECTED]
> > Reply-To: [EMAIL PROTECTED]
> > Hi Wolfgang!
> > The current avro spec mentions that when HTTP is being used as a
> transport for an Avro-defined protocol that the content type 'avro/binary'
> should be used. There's an open issue about this not being a valid
> content type, though there hasn't been movement in a while.
> > AFAICT, this means there isn't a general best practice at the moment. I
> have some ideas on the matter, perhaps we could discuss this on the dev
> list and then update the relevant jira?
> > -Sean
> > : http://avro.apache.org/docs/current/spec.html#HTTP+as+Transport
> > : https://issues.apache.org/jira/browse/AVRO-488
> > On Mon, Oct 22, 2012 at 5:04 PM, Wolfgang Hoschek <
> [EMAIL PROTECTED]> wrote:
> > What's the preferred mime type for binary avro and json formatted avro
> files that I should use in an app?
> > For example "application/avro+binary", "application/avro+json"?
> > Thanks,
> > Wolfgang
> > --
> > Sean Busbey
> > Solutions Architect
> > Cloudera, Inc.