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

Protection needed to arbitrate station requests and server requests #27

Closed
elondaits opened this issue Sep 12, 2016 · 2 comments
Closed
Assignees
Labels

Comments

@elondaits
Copy link

elondaits commented Sep 12, 2016

If a station starts on its own it'll try to start an application. If a server starts the station it'll also try to start an application. Some arbitration is needed so both things don't conflict.

e.g. An explicit API running in the station for switching apps which has some sort of locking or IPC mechanism (lock or queue). Requests from the server fail if there's a local app switch.

@malex984
Copy link
Member

It has to be part of Hilbert-CLI-Server / Hilbert-CLI-Station design: #28

@malex984
Copy link
Member

Currently Hilbert client-side bash script (hilbert-station) uses a lockfile to prevent two actions running in the same time. In case of a lock script execution will fail with an error code 2 (see start_locking in tools/hilbert-station)

@malex984 malex984 added this to the Hilbert-CLI Design milestone Dec 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants