[
https://issues.apache.org/jira/browse/THRIFT-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764576#comment-16764576
]
Satyender Yadav commented on THRIFT-4777:
-----------------------------------------
[~allengeorge] You are definitely right when we look at the Client side code to
be async. It requires lots of changes to be usable in async manner.
On Server side code however, reading from TCP and replying back to after
processing needs the read & write handlers to be async first, then the process
itself. I am to divide the tasks, it would be three layers
IO (Server Side) | Server Side Process (Basically the implementation of
generated server side stub) | Client Side generated code
In this Jira I am targeting making the Server Side IO to be async, which should
be followed by making the processing function and client logic async as well.
Also I have realised that to make server side IO implementation async, I need
to have both transport and protocol traits to be of kind Future. Hence changes
in transport and protocol are required. Please let me know if it can be avoided.
> Non Blocking Server implementation for Rust
> -------------------------------------------
>
> Key: THRIFT-4777
> URL: https://issues.apache.org/jira/browse/THRIFT-4777
> Project: Thrift
> Issue Type: New Feature
> Components: Rust - Library
> Reporter: Satyender Yadav
> Assignee: Allen George
> Priority: Minor
>
> Implement Non blocking server in Thrift rust library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
