Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we restrict number of open connection at client side itself #69

Open
TaslimAlam opened this issue Nov 19, 2018 · 3 comments
Open

Can we restrict number of open connection at client side itself #69

TaslimAlam opened this issue Nov 19, 2018 · 3 comments
Labels

Comments

@TaslimAlam
Copy link

Hi,

Cisco system recommends that client must not open more than 3 connection at a time at RPC server.

Is there any way we can achieve these?

Regards

@kofemann
Copy link
Member

Well, technically, a single client uses only a singe connection. However, I can imagine an application, that create's a new rpc client per request and may have multiple requests in parallel. In such cache you either should share a single client with multiple threads/requests or have some king of rpc client pool with a limit.

@TaslimAlam
Copy link
Author

TaslimAlam commented Dec 4, 2018

Hi Kofemann,,

I am in situation where I will be implementing asynchronous call to RPC server where it won't return any results as response. However after calling rpcClient.call() method, is there any any way that we can ensure that the call has been accepted and client needs to be closed.

Please help me on this query.

@kofemann
Copy link
Member

kofemann commented Dec 6, 2018

@TaslimAlam If i understand you correctly, then you need to use RpcCall#call with completion handler, which will asynchronously call CompletionHandler#completed when call complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants