The Sentry Service Client does not allow for connection pooling because there is no way to:
1) Detect that a connection is broken
2) Re-open a broken connection
This would allow for Sentry Service clients to implement connection pooling like:
Currently, the only way to ensure connections are not broken is to open a new connection before every RPC.
|[UnitTest] In Kerberos mode, client should run under clientSubject||Resolved|
|Extend SentryClient by SentryClientInvocationHandler||Resolved|
|Create connection pool factory||Resolved|