[
https://issues.apache.org/jira/browse/THRIFT-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992945#comment-15992945
]
Mark Erickson edited comment on THRIFT-4187 at 5/2/17 2:00 PM:
---------------------------------------------------------------
[~allengeorge] I agree with your conclusions and the assessment that the
challenge with the Dart implementation is adapting an async (non-blocking)
system to a blocking-style API. If Dart needs to support reading the header in
a separate message from the body, then there will be some rework needed to
collect messages in the buffer before attempting to read. I haven't put much
thought into it lately, but let me know if you get stuck and I (or some of my
colleagues) can try to help.
was (Author: markerickson-wk):
[~allengeorge] I agree with your conclusions and the assessment that the
challenge with the Dart implementation is adapting an async (non-blocking)
system to a blocking-style calls. If Dart needs to support reading the header
in a separate message from the body, then there will be some rework needed to
collect messages in the buffer before attempting to read. I haven't put much
thought into it lately, but let me know if you get stuck and I (or some of my
colleagues) can try to help.
> 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)
