You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
@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.
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
The text was updated successfully, but these errors were encountered: