[
https://issues.apache.org/jira/browse/THRIFT-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935222#comment-14935222
]
Nobuaki Sukegawa commented on THRIFT-3359:
------------------------------------------
Yes, we should choose whatever works best for us.
I just wanted to make it clear that any standard library will encode padding
and there's most often no way to disable it (sounds extra efforts if we don't
allow padding).
But since we've been agreeing on the approach from the beginning it was only an
extra noise, I guess.
Anyway, I still think we should document our choice in the header file comment
so that any new implementation of TJSONProtocol can avoid this problem.
I might include a draft (a line or two) to the patch but would happily leave it
to others more fluent in English.
> 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)
