[
https://issues.apache.org/jira/browse/RATIS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211616#comment-17211616
]
Tsz-wo Sze commented on RATIS-1030:
-----------------------------------
Yes, we will need two different client impls so that the code won't mix
together. It is similar to OrderedAsync and UnorderedAsync -- they are for
code separation.
For the user API, we may add
{code}
// RaftClient
DataStreamApi getDataStreamApi();
{code}
so that users always starts with RaftClient (see also
RaftClient.getMessageStreamApi()). It probably is easier for the users.
> Implement ratis streaming using netty - Client code
> ---------------------------------------------------
>
> Key: RATIS-1030
> URL: https://issues.apache.org/jira/browse/RATIS-1030
> Project: Ratis
> Issue Type: Sub-task
> Components: Streaming
> Reporter: Ansh Khanna
> Assignee: Ansh Khanna
> Priority: Major
> Fix For: 1.1.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This is the client side code of RATIS-1012.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
