[
https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109686#comment-14109686
]
Roger Meier commented on THRIFT-2674:
-------------------------------------
I've registered the following records @ IANA:
http://www.iana.org/form/media-types
|*Subtype name*|*Encoding considerations*|
|vnd.apache.thrift.binary|binary|
|vnd.apache.thrift.json|8 bit text|
|apache.thrift.compact|binary|
|*Security considerations*| Apache Thrift does not enforce a security
mechanism. Users define security features at application or transport level.|
|*Interoperability considerations*|Today only x-thrift is used and we have
different protocols.|
|*Published specification*| http://thrift.apache.org|
|*Applications which use this media type*|Users do specify their own data
structures and services via an interface description language (IDL) to
communicate fast across languages and platforms.|
|*Restrictions on usage*|no restrictions, software is Apache License:
http://www.apache.org/licenses/LICENSE-2.0|
|*Indended Usage*| Efficient communication across languages and platforms.|
I will keep you up-to-date on this!
;-r
> JavaScript: declare Accept: and Content-Type: in request
> --------------------------------------------------------
>
> Key: THRIFT-2674
> URL: https://issues.apache.org/jira/browse/THRIFT-2674
> Project: Thrift
> Issue Type: Bug
> Components: JavaScript - Library
> Reporter: Stig Bakken
> Priority: Minor
>
> When a JS client communicates with a backend supporting several encodings,
> knowing which protocol to use is a bit kludgy. This patch tries to fix that
> by always setting the Accept: and Content-Type: request headers to
> "application/json".
--
This message was sent by Atlassian JIRA
(v6.2#6252)
