Github user dthaluru commented on the issue:
https://github.com/apache/thrift/pull/1251
One of the main reason I had separate transport for Nonblocking is,
blocking has a feature called interruptible which does not really apply for
nonblocking. And additional api's are added for Nonblockingtransport which are
not required in blockingtransport.
And currently TSSLSocket underlying implementation is Nonblocking by
default and uses select api.
TNonblockingServer implementation uses libevent which inturn calls select
api's. We cannot use libevent with select as there will be a race condition
between select and libevent as both poll for events on registered sockets.
Ideally there should be another class called TNonblockingSSLSocket which can be
used with NonblockingServers.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
