[
https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157140#comment-14157140
]
Randy Abernethy commented on THRIFT-2674:
-----------------------------------------
Hey Jens,
Thanks for the cross post. You are right, there are not too many registered
suffixes (8 in total).
http://www.iana.org/assignments/media-type-structured-suffix/media-type-structured-suffix.xhtml
The +xml and +json suffixes are widely used and supported though. A lot of
+json and +xml here:
http://www.iana.org/assignments/media-types/media-types.xhtml
Java Libs like Moxy and Jackson will automatically convert POJOs to/from media
types with +xml or +json suffixes, other language REST frameworks have similar
support. It is not a lot of work to make them do it for .json, its just not
free.
-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
> Attachments: js-type.diff
>
>
> 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.3.4#6332)
