Skip to content

Do not expose $master property and accept any ServerInterface for SecureServer #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 8, 2017

Conversation

clue
Copy link
Member

@clue clue commented Feb 8, 2017

Interfering with this (previously public) property could introduce some very subtle bugs, so it's best to simply avoid exposing it.

Empirical evidence seems to suggest this isn't used much outside of this package anyway.

Inside this package, we can safely replace all references to it with references to child sockets created upon connection.

Also, the SecureServer now supports any underlying ServerInterface (advanced usage) and no longer relies on a concrete implementation.

Builds on top of #69

clue added 2 commits February 8, 2017 12:02
Interfering with this (previously public) property could introduce some
very subtle bugs, so it's best to simply avoid exposing it.

Empirical evidence seems to suggest this isn't used much outside of this
package anyway.

Inside this package, we can safely replace all references to it with
references to child sockets created upon connection.
@clue clue added this to the v0.5.0 milestone Feb 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants