Github user nsuke commented on the issue:
https://github.com/apache/thrift/pull/1114
@dthaluru I think we can avoid duplicating the entire client stack.
As far as I can see the only thing that really matters is
`TNonblockingSSLSocket`.
If we make it compatible with `TNonblockingTransport`, almost anything else
would not be needed any longer.
The most significant incompatibility is `int read(ByteBuffer)` v.s.
`ByteBuffer read(int)`.
Would it be possible for `TNonblockingSSLSocket` to accept and reuse
`ByteBuffer` so that the method signature can be the same ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
