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.

Sign up for GitHub

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

Jump to bottom

Define values for CPU architecture #106

Merged
merged 5 commits into from May 27, 2020
Merged

Define values for CPU architecture #106

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
bedefcb
Define values for CPU architecture
yoavweiss May 4, 2020
75ef4e9
Add 64bit variants to the CPU map
yoavweiss May 8, 2020
ccbc2e6
s/arm_64/arm64/
yoavweiss May 10, 2020
835876e
Remove bitness and correct typo
yoavweiss May 12, 2020
7b6d4c6
Merge branch 'master' into arch_definition
yoavweiss May 19, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 14 additions & 0 deletions index.bs
View file
Open in desktop
Expand Up @@ -191,9 +191,23 @@ has defined a number of properties for itself:
* <dfn for="user agent" export>mobileness</dfn> - A boolean indicating if the [=user agent=]'s
device is a mobile device. (for example: ?0 or ?1)


[=User agents=] SHOULD keep these strings short and to the point, but servers MUST accept arbitrary
values for each, as they are all values constructed at the [=user agent=]'s whim.

[=User agents=] MUST map higher-entropy [=platform architecture=] values to the following buckets:

* x86 CPU architectures => "x86"
* ARM CPU architectures => "arm"
yoavweiss marked this conversation as resolved.
Show resolved Hide resolved

Other CPU architectures could be mapped into one of these values in case that makes sense, or be
mapped to the empty string.
yoavweiss marked this conversation as resolved.
Show resolved Hide resolved

ISSUE 105: There might be use-cases for higher-entropy, more specific CPU architectures (e.g. 32
vs. 64 bit architectures, or specific instruction sets for the download of highly optimized
executable binaries). If necessary, we could support those use-cases through one or more separate
hints.

[=User agents=] SHOULD return the empty string or a fictitious value for [=platform architecture=]
unless the user's platform is one where both the following conditions apply:
* Binary download of executables is likely.
Expand Down