[
https://issues.apache.org/jira/browse/THRIFT-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689715#action_12689715
]
Bryan Duxbury commented on THRIFT-409:
--------------------------------------
I see what you're saying about incremental roll-out. At the cost of one
additional byte, it might be worth it to keep the same wire format. To make the
code efficient, though, I don't think that a union should include the logic for
"skipping" subsequent fields. That is, I don't want to write a loop at all in
the read() method, so it might just look like, read field id, read type, read
value, read stop, if not stop, throw protocol exception.
> Add "union" to Thrift
> ---------------------
>
> Key: THRIFT-409
> URL: https://issues.apache.org/jira/browse/THRIFT-409
> Project: Thrift
> Issue Type: New Feature
> Reporter: Bryan Duxbury
> Fix For: 0.2
>
>
> It would be very helpful to have a "union" construct in Thrift. Let's decide
> on the design and then break up into sub-issues to add this feature.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
