[
https://issues.apache.org/jira/browse/THRIFT-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613732#action_12613732
]
David Reiss commented on THRIFT-31:
-----------------------------------
I guess so, but it seems like it is not a protocol-specific check. Doing it in
the generated code means we don't need that check in every protocol.
> More validation during serialization
> ------------------------------------
>
> Key: THRIFT-31
> URL: https://issues.apache.org/jira/browse/THRIFT-31
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (Java), Library (Java)
> Reporter: Johan Stuyts
> Attachments: MoreValidationDuringSerialization.patch
>
>
> The protocols and the generated code can perform more validation during
> deserialization. The additional validations are:
> - check the size of strings, binaries and containers is >= zero (protocols)
> - check if the name of the structure is correct (if present) (structures)
> - check if the field type is valid (structures)
> - check if container elements have the correct type (structures)
> - check if the call message has the correct type (processors)
> - check if the reply message has the correct type (clients)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
