You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2008/12/18 01:38:44 UTC
[jira] Updated: (THRIFT-236) Structs should be serialized in a
consistent order
[ https://issues.apache.org/jira/browse/THRIFT-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Duxbury updated THRIFT-236:
---------------------------------
Patch Info: [Patch Available]
> Structs should be serialized in a consistent order
> --------------------------------------------------
>
> Key: THRIFT-236
> URL: https://issues.apache.org/jira/browse/THRIFT-236
> Project: Thrift
> Issue Type: Improvement
> Reporter: Bryan Duxbury
> Attachments: thrift-236.patch
>
>
> As it stands right now, Ruby generated structs will be serialized in arbitrary order (due to storage of metadata in a hash). This leads to different binary encoding for the same struct values. Ideally, it should be the same for any two serializations of equivalent structs, and between languages if possible.
> The two approaches that seem to make the most sense are in lowest-to-highest field id order, and in IDL-defined order. What do people think of this idea, and which approach would be preferred?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.