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

Make it possible to respond with different version arguments based on is_machine parameter on update check #24

Open
shashkin opened this issue Dec 25, 2014 · 1 comment

Comments

@shashkin
Copy link
Contributor

When talking about Omaha+Chromium, there is already workaround for Chromium inside Omaha client code, which handles this scenario on client side.

In general, however, it would be great if the server can manage this by itself so we don't depend on any particular application like Chromium.

@shashkin shashkin changed the title Make it possible on update check to respond with different version arguments based on is_machine parameter Make it possible to respond with different version arguments based on is_machine parameter on update check Dec 25, 2014
@shashkin
Copy link
Contributor Author

Possible design change: split "Arguments" field of Omaha Version into three fields:

  • "Common arguments" - arguments which are the same for per-user and per-machine installations
  • "Per-user arguments" - arguments only applicable for per-user installation
  • "Per-machine arguments" - arguments only applicable for per-machine installation

Depending on is_machine value, the server will respond arguments as concatenation of "common" and "per-user/per-machine" arguments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant