You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2017/05/02 03:22:04 UTC

[jira] [Comment Edited] (THRIFT-4187) Dart -> Rust Framed cross tests fail

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

James E. King, III edited comment on THRIFT-4187 at 5/2/17 3:21 AM:
--------------------------------------------------------------------

I'd say the Dart client is at fault.  RPC systems should never rely on the size of a frame, since it can change too easily.  Just add a VPN client to your system and your MTU might change when connecting to some systems, for example.  Then again, having rust send once is more efficient, so that should be done anyway BUT only if it doesn't impose memory requirements that are too onerous to buffer the entire message just to prepend the length.


was (Author: jking3):
I'd say the Dart client is at fault.  RPC systems should never rely on the size of a frame, since it can change too easily.  Just add a VPN client to your system and your MTU might change when connecting to some systems, for example.  

> Dart -> Rust Framed cross tests fail
> ------------------------------------
>
>                 Key: THRIFT-4187
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4187
>             Project: Thrift
>          Issue Type: Bug
>          Components: Rust - Library
>            Reporter: Allen George
>            Assignee: Allen George
>            Priority: Minor
>
> For some reason the Dart (client) -> Rust (server) framed-transport cross tests fail. Initial investigation shows that *somehow* the dart client think the socket was closed, which means it doesn't read the message from the underlying transport.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)