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/07/12 07:14:33 UTC
[jira] Commented: (THRIFT-31) More validation during serialization
[ https://issues.apache.org/jira/browse/THRIFT-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613051#action_12613051 ]
Bryan Duxbury commented on THRIFT-31:
-------------------------------------
If there's debate about performance impact, I think we should remove the struct name stuff from the generator, but keep the size checking stuff. If these fixes were in, it'd make failure cases (which I just dealt with) a lot more consistent with my expectations.
> 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.