[jira] Issue Comment Edited: (THRIFT-313) BinaryProtocolAccelerated and BinaryProtocol don't produce the same bytes when writes aren't strict

["Jon Dugan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672865#action_12672865 ] 

jdugan edited comment on THRIFT-313 at 2/11/09 7:30 PM:
-----------------------------------------------------------

I think there is a similar bug in the Python library.  See THRIFT-340.

      was (Author: jdugan):
    I think there is a similar bug in the Python library.
  
> BinaryProtocolAccelerated and BinaryProtocol don't produce the same bytes when writes aren't strict
> ---------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-313
>                 URL: https://issues.apache.org/jira/browse/THRIFT-313
>             Project: Thrift
>          Issue Type: Bug
>          Components: Library (Ruby)
>            Reporter: Kevin Clark
>            Priority: Blocker
>             Fix For: 0.1
>
>
> The Ruby and C versions do slightly different things:
> 1)
> 'Thrift::BinaryProtocolAccelerated should write the message header without version when writes are not strict' FAILED
> expected: "\000\000\000\vtestMessage\001\000\000\000\021",
>      got: "\000\000\000\vtestMessage\003\000\000\000\021" (using ==)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.