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

Ambiguous use of Client in the codebase. #2

Closed
charlie-ht opened this issue Dec 19, 2015 · 1 comment
Closed

Ambiguous use of Client in the codebase. #2

charlie-ht opened this issue Dec 19, 2015 · 1 comment

Comments

@charlie-ht
Copy link
Contributor

The Client class is really the thing communicating with us on the other side of the websocket. We're using the term to refer to the thing the server is communicating with on behalf of the thing on on the other side of the websocket... :-)

Emacs refers to what we're currently calling Client as an "inferior". Per notes this probably not widely known nomenclature. We should decide on something less ambiguous, and then perform the refactoring.

Current candidates:

  • Application
  • Worker
  • HostApplication
  • HostProcess

I'll defer to Per on the naming, I'll go with anything other than Client.

@PerBothner
Copy link
Owner

Also worth considering:

  • Backend

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

No branches or pull requests

2 participants