[ https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105823#comment-14105823 ]
Randy Abernethy commented on THRIFT-2674: ----------------------------------------- Hey Stig, There's work going on to add TBinaryProtocol and TCompact protocol to the browser side (they are already present in Node). Give the three possible encodings and the presence of "application/thrift" in other languages what do you think about this: TJSONProtocol: application/thrift+json TBinaryProtocol: application/thrift TCompactProtocol: application/thrift.compact or some such? -Randy > 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)