Github user cherrot commented on the pull request:
https://github.com/apache/thrift/pull/945#issuecomment-195951383
>readable sockets may mean dropped connections.
@nsuke Actually I didn't figure out what you mean. How can dropped
connections (I mean, those in CLOSE_WAIT / CLOSE state) be __OPENED__
connections?
When I'm calling this method, what I expect is getting the correct
underlying connection state, not just telling me if I have closed it by hand.
Or otherwise, __how could I determine when I need reconnect the underlying
connection instead of sending to / reading from it directly?__
Also, I referred to the 3rd party lib because I want to show that it's a
common pattern to judge if a connection could be used, not because the LICENSE.
I could reimplement this 10-line-code-block in my style if you guys prefer that
:)
---
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.
---
