It only has one connection, why does it need a set of them?
Makes ~RSocketClient destroy the RSocketStateMachine synchronously, where
previously this was async. I'm worried about users destroying their
RSocketClient objects, and then having their EventBases accidentally access more
state later via stream subscribers.
It only has one connection, why does it need a set of them?
Makes ~RSocketClient destroy the RSocketStateMachine synchronously, where previously this was async. I'm worried about users destroying their RSocketClient objects, and then having their EventBases accidentally access more state later via stream subscribers.