You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King III (JIRA)" <ji...@apache.org> on 2019/01/11 22:29:00 UTC
[jira] [Updated] (THRIFT-3250) Apache Thrift should use registered
media types with HTTP
[ https://issues.apache.org/jira/browse/THRIFT-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James E. King III updated THRIFT-3250:
--------------------------------------
Component/s: (was: Ruby - Library)
(was: Python - Library)
(was: PHP - Library)
(was: Perl - Library)
(was: Node.js - Library)
(was: JavaScript - Library)
(was: JavaME - Library)
(was: Java - Library)
(was: Haxe - Library)
(was: Haskell - Library)
(was: Go - Library)
(was: Erlang - Library)
(was: Delphi - Library)
(was: Dart - Library)
(was: D - Library)
(was: Cocoa - Library)
(was: C++ - Library)
(was: C# - Library)
(was: AS3 - Library)
(was: .NETCore - Library)
Wish List
> Apache Thrift should use registered media types with HTTP
> ---------------------------------------------------------
>
> Key: THRIFT-3250
> URL: https://issues.apache.org/jira/browse/THRIFT-3250
> Project: Thrift
> Issue Type: Improvement
> Components: Wish List
> Affects Versions: 0.9.3
> Environment: all
> Reporter: Randy Abernethy
> Assignee: Randy Abernethy
> Priority: Minor
>
> Now that we have registered media types:
> - application/vnd.apache.thrift.binary
> - application/vnd.apache.thrift.compact
> - application/vnd.apache.thrift.json
> We should use them exclusively, replacing the old x-thrift. I suggest TProtocol gain a getMediaType() method which returns the correct media type when invoked on a concrete protocol (e.g. TBinaryProtocol.getMediaType() would return "application/vnd.apache.thrift.binary".
> HTTP oriented code can then invoke the getMediaType() method of the protocol to discover the correct media type to set in HTTP headers.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)