transportActive and transportInactive
Summary: These are equivalents to Netty's channelActive and channelInactive, but we've been calling channels transports so I'm staying consistent. I skipped integrating this into TAsyncTransportHandler because thrift still does manual CB attachment/detachment and it's unclear how that fits into this model If my suspicions are correct, it *should* be possible to make attachReadCallback and detachReadCallback private in AsyncSocketHandler, right? And perhaps get rid of the event base modifier methods? What's our use case for those? Test Plan: unit, employ in telnet server Reviewed By: davejwatson@fb.com Subscribers: fugalh, alandau, bmatheny, folly-diffs@, jsedgwick, yfeldblum, chalfant FB internal diff: D2044520 Signature: t1:2044520:1431551998:af1de358b5dbefcca148814015d8e9f63f458d5d
Showing
Please register or sign in to comment