[jira] [Resolved] (THRIFT-2985) TFramedTransport should handle writing data larger than the max frame size

["James E. King III (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/THRIFT-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James E. King III resolved THRIFT-2985.
---------------------------------------
       Resolution: Won't Do
         Assignee: James E. King III
    Fix Version/s: 1.0

As support for the older cocoa compiler and library have been removed (see THRIFT-4719), all of the issues in Jira related to that code have also been removed.  For legacy cocoa support you can use version 0.12.0 - everyone is expected to move to swift if they want to use the next release of Thrift.

> TFramedTransport should handle writing data larger than the max frame size
> --------------------------------------------------------------------------
>
>                 Key: THRIFT-2985
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2985
>             Project: Thrift
>          Issue Type: Bug
>          Components: Cocoa - Library
>    Affects Versions: 0.9.2
>            Reporter: Jeremy W. Sherman
>            Assignee: James E. King III
>            Priority: Major
>             Fix For: 1.0
>
>
> TFramedTransport frames its messages with a 32-bit unsigned integer in network byte order. It writes only when -flush is called.
> However, it can buffer an unlimited amount of data prior to flush being called, and on 64-bit platforms, it can be requested to buffer more than UINT32_MAX in a single write call.
> It should handle breaking a single large buffer into several framed buffers for writing during flush.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)