[
https://issues.apache.org/jira/browse/THRIFT-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934337#comment-14934337
]
Nobuaki Sukegawa commented on THRIFT-3359:
------------------------------------------
As I pointed out in the last comment, padding is actually mandatory unless we
explicitly state otherwise.
{quote}
Implementations *MUST* include appropriate pad characters at the end of
encoded data unless the specification referring to this document
explicitly states otherwise.
{quote}
(emphasis mine, from the same link)
It would be good idea to take this opportunity to add the "opt out" statement
to existing JSON protocol spec.
Although I could only find any specification but a header comment in C++
TJSONProtocol.h.
{quote}
* 4. Thrift binary values are encoded into Base64 and emitted as JSON strings.
{quote}
> Binary field incompatibilities
> ------------------------------
>
> Key: THRIFT-3359
> URL: https://issues.apache.org/jira/browse/THRIFT-3359
> Project: Thrift
> Issue Type: Bug
> Components: C# - Library, C++ - Library, Java - Library, JavaScript
> - Library, Node.js - Library, Python - Library
> Affects Versions: 0.9.3
> Reporter: Nobuaki Sukegawa
> Assignee: Nobuaki Sukegawa
> Fix For: 0.9.4
>
>
> Binary fields in TJSONProtocols of many languages are incompatible to each
> other.
> Also, those in all protocols of NodeJS cannot reliably talk to other
> languages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
