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

Chorus Hub should not fail if multiple instances are running #178

Open
mikelothers opened this issue Jul 11, 2018 · 2 comments
Open

Chorus Hub should not fail if multiple instances are running #178

mikelothers opened this issue Jul 11, 2018 · 2 comments

Comments

@mikelothers
Copy link

This is a report on behalf of Peter Wulfing...
Currently, if multiple instances of Chorus Hub are running, it does not work. Also, it is difficult to determine that more than one instance is running without examining each person's computer.

Possible fixes:

  • Chorus Hub should notify the user that multiple instances are running and allow him/her to choose which one they want to use.
  • John Hatton proposed a less-expensive fix: All Chorus Hub instances should detect each other and put up a message saying that you have to turn off all but one.
@hatton
Copy link
Member

hatton commented Jul 11, 2018

Actually nowadays it's a service (at least on Windows) so I don't know if it's difficult to put up UI? If the client apps could detect the situation, they could give the notice instead.

@wasta-mxb
Copy link

It being a service which survives re-boot and having no UI is perhaps a problem. Un-sophisticated users have no idea it is running, or how to turn it off. Having the clients detect it is one option, but there are at least three (PText, FLEx and WeSay) which would have to be modified to be sensitive to this.
A simple ON/OFF switch would be preferable, even if this was a separate program.

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

3 participants