You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by Wolfgang Hoschek <wo...@mac.com> on 2012/10/23 00:08:15 UTC
Fwd: Avro mime type
Forwarding this question to dev list per Sean's suggestion.
Wolfgang.
Begin forwarded message:
> From: Sean Busbey <bu...@cloudera.com>
> Subject: Re: Avro mime type
> Date: October 22, 2012 2:58:10 PM PDT
> To: user@avro.apache.org
> Reply-To: user@avro.apache.org
>
> 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.[1] There's an open issue[2] 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
>
> [1]: http://avro.apache.org/docs/current/spec.html#HTTP+as+Transport
> [2]: https://issues.apache.org/jira/browse/AVRO-488
>
> On Mon, Oct 22, 2012 at 5:04 PM, Wolfgang Hoschek <wo...@mac.com> 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.
>
Re: Avro mime type
Posted by Sean Busbey <bu...@cloudera.com>.
Hi All!
For the curious, the process of getting a new IANA content type is covered
by RFC4288[1].
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
application/vnd.apache.avro+binary
application/vnd.apache.avro+json
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.
-Sean
[1]: http://tools.ietf.org/rfc/rfc4288.txt
On Mon, Oct 22, 2012 at 6:08 PM, Wolfgang Hoschek
<wo...@mac.com>wrote:
> Forwarding this question to dev list per Sean's suggestion.
>
> Wolfgang.
>
> Begin forwarded message:
>
> > From: Sean Busbey <bu...@cloudera.com>
> > Subject: Re: Avro mime type
> > Date: October 22, 2012 2:58:10 PM PDT
> > To: user@avro.apache.org
> > Reply-To: user@avro.apache.org
> >
> > 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.[1] There's an open issue[2] 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
> >
> > [1]: http://avro.apache.org/docs/current/spec.html#HTTP+as+Transport
> > [2]: https://issues.apache.org/jira/browse/AVRO-488
> >
> > On Mon, Oct 22, 2012 at 5:04 PM, Wolfgang Hoschek <
> wolfgang.hoschek@mac.com> 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.
> >
>
>
--
Sean Busbey
Solutions Architect
Cloudera, Inc.