Skip to content
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

Rename sender/receiver to client/server #23

Merged
merged 1 commit into from
Feb 4, 2020

Conversation

markmandel
Copy link
Member

Changes the nomenclature to being "client proxy" and "server proxy", which is far easier to understand, both from a user perspective, and from a code perspective.

Closes #22

Changes the nomenclature to being "client proxy" and "server proxy",
which is far easier to understand, both from a user perspective, and
from a code perspective.

Closes #22
@markmandel markmandel added kind/documentation Improvements or additions to documentation area/user-experience Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc kind/cleanup Refactoring code, fixing up documentation, etc labels Feb 4, 2020
@markmandel markmandel requested a review from suom1 February 4, 2020 18:54
@markmandel markmandel merged commit 6f90328 into master Feb 4, 2020
@markmandel markmandel deleted the refactor/client-server branch February 4, 2020 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/user-experience Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc kind/cleanup Refactoring code, fixing up documentation, etc kind/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should sender/receiver be client/server as concepts?
3 participants