[
https://issues.apache.org/jira/browse/HBASE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15678067#comment-15678067
]
Xiaobing Zhou edited comment on HBASE-17051 at 11/18/16 11:14 PM:
------------------------------------------------------------------
I posted the initial patch v000, and will add tests in next patch.
# built User class with user name only inside for simplicity.
# built ConnectionId class that packs user and server info(i.e.
hbase::pb::ServerName), which is used to identify connection uniquely.
# built RpcConnection class that packs ConnectionId and HBaseService (i.e.
wangle::Service<std::unique_ptr<Request>, Response>). HBaseService represents
various remote RPC APIs HBase implemented. RpcConnection will forward requests
to HBaseService.
# built RpcClient that handles lifecycle of RpcConnections and offers
sync/async call.
was (Author: xiaobingo):
I posted the initial patch v000, and will add tests in next patch.
#built User class with user name only inside for simplicity.
#built ConnectionId class that packs user and server info(i.e.
hbase::pb::ServerName), which is used to identify connection uniquely.
#built RpcConnection class that packs ConnectionId and HBaseService (i.e.
wangle::Service<std::unique_ptr<Request>, Response>). HBaseService represents
various remote RPC APIs HBase implemented. RpcConnection will forward requests
to HBaseService.
#built RpcClient that handles lifecycle of RpcConnections and offers sync/async
call.
> libhbase++: implement RPC client and connection management
> ----------------------------------------------------------
>
> Key: HBASE-17051
> URL: https://issues.apache.org/jira/browse/HBASE-17051
> Project: HBase
> Issue Type: Sub-task
> Reporter: Xiaobing Zhou
> Assignee: Xiaobing Zhou
> Attachments: HBASE-17051-HBASE-14850.000.patch
>
>
> This proposes building RPC client and connection management layer, which
> supports the equivalent functions resides in RpcClient.java and
> RpcConnection.java. Specifically, handler/pipeline concepts will be used for
> implementation, similar to NettyRpcClient and NettyRpcConnection in java side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
