Skip to content

Conversation

@michaelklishin
Copy link
Contributor

@michaelklishin michaelklishin commented Sep 17, 2020

This undoes #758 (introduced in response to #515).

The events make more sense in the primary IConnection interface.
Most users enable automatic connection recovery and asking them to
cast to IAutorecoveringConnection is counter-intuitive.

As suggested in #515, we add no-op add and remove handlers
so that IConnection is easier to implement/mock.

See #940 for the discussion.

Closes #940, expected to go into 7.0 only.

This undoes #758 (made in response to #515).

The events make more sense in the primary IConnection interface.
Most users enable automatic connection recovery and asking them to
cast to IAutorecoveringConnection is counter-intuitive.

As suggested in #515, we add no-op add and remove handlers
so that IConnection is easier to implement/mock.

See #940 for the discussion.

Closes #940.
@lukebakken lukebakken added this to the 7.0.0 milestone Sep 17, 2020
@michaelklishin michaelklishin removed this from the 7.0.0 milestone Sep 18, 2020
@michaelklishin michaelklishin merged commit 88001ce into master Sep 19, 2020
@michaelklishin michaelklishin deleted the mk-recovery-events-in-iconnection branch September 19, 2020 01:37
@michaelklishin
Copy link
Contributor Author

Merging because we seem to have reached a consensus in #940: this is a better way forward compared to #758.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Discussion: recovery events for automatically recovering connections (IAutoRecoveringConnection)

3 participants