Closed dkormalev closed 7 years ago
can you explain the rationale for switching from a singleshot timer to needing a fully allocated QTimer for reconnect? (It occurs to me that you wouldn't have had to fix the second bullet point if you hadn't added a QTimer for reconnect).
Also, regarding forceDisconnectFromHost
, I think it should more closely follow the API of QAbstractSocket and use the term abort
+1 for abort, will replace. BTW, probably with this naming it shouldn't send close message but simply disconnects, what do you think?
About fully allocated QTImer. It is still singleShot. The reason why I need it allocated somewhere to be able to stop it at disconnectFromHost or new connectFromHost.
Yeah I agree, if you're forcing the connection to abort there shouldn't be any expectation that the action is graceful.
LGTM, thanks for the contribution