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 2010/04/22 03:33:51 UTC
[jira] Commented: (THRIFT-760) Generated client code does not set
or check the sequence ID in messages
[ https://issues.apache.org/jira/browse/THRIFT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859620#action_12859620 ]
Bryan Duxbury commented on THRIFT-760:
--------------------------------------
I think this is generally cool, but won't it break Java's ability to interact with any language that doesn't implement the seqid functionality yet? My impression is that we've left the capability, but not yet implemented it anywhere.
> Generated client code does not set or check the sequence ID in messages
> -----------------------------------------------------------------------
>
> Key: THRIFT-760
> URL: https://issues.apache.org/jira/browse/THRIFT-760
> Project: Thrift
> Issue Type: Bug
> Components: Compiler (Java)
> Affects Versions: 0.2
> Reporter: James Grant
> Priority: Minor
> Attachments: thrift-seqid.patch
>
>
> The sequence ID is never set in the generated client code. It is also never checked. This means that if you continue to use a connection after a socket timeout the returned results can arrive out of sequence. When this happens an exception should be thrown so that incorrect results are never returned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.