[jira] [Issue Comment Edited] (THRIFT-1239) TupleProtocol- An extremely compact, temporary protocol

["Armaan Sarkar (JIRA)" <ji...@apache.org>]

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

Armaan Sarkar edited comment on THRIFT-1239 at 7/19/11 9:56 PM:
----------------------------------------------------------------

This issue depends on the pluggable serializer because the TupleProtocol relies on changes in the read/write methods of an object.

      was (Author: armaansarkar):
    The TupleProtocol relies on changes in the read/write methods of an object
  
> TupleProtocol- An extremely compact, temporary protocol
> -------------------------------------------------------
>
>                 Key: THRIFT-1239
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1239
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Java - Compiler
>            Reporter: Armaan Sarkar
>            Priority: Minor
>
> Currently, protocols are built to be pretty robust to 'schema' changes. This is done by sending metadata about when a struct or a field will start/end, the number of fields to expect and the types of each field, etc. However, there are cases when the recipient knows all of this, even before it receives this metadata. In these cases, sending the metadata unnecessarily eats up bandwidth. The TupleProtocol rectifies this by sending and receiving only the value of each field in a specified order. The only metadata passed is about variable information such as the size of a container or which optional fields are set.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira