[
https://issues.apache.org/jira/browse/HBASE-16433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426590#comment-15426590
]
stack commented on HBASE-16433:
-------------------------------
Makes sense putting back the pb interface as the boundary between rpc engine
and user of the rpc. [~jurmous] has a form of this in his
createProtobufRpcChannel If we could keep netty behind this Interface, that'd
be cleanest (if awkward). Good by you [~jurmous]?
On grpc, not yet or not here, not on this port. We need to finish shading
project first so can change the pb version. If we were to do grpc, it should be
on a different port (under the UI port since we already advertise an http
service here?)
> Remove AsyncRpcChannel related stuffs
> -------------------------------------
>
> Key: HBASE-16433
> URL: https://issues.apache.org/jira/browse/HBASE-16433
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-16433.patch
>
>
> AsyncRpcChannel can not be used by protobuf stub. We should implement the
> async logic along with the RpcChannel interface of protobuf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
