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

Address limits on unconstrained inputs #520

Merged
merged 7 commits into from
Jan 16, 2023
Merged

Address limits on unconstrained inputs #520

Changes from 2 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
5c28a2d
Address limits on unconstrained inputs
annevk Jan 9, 2023
815c387
acknowledge that limits are a tracking vector
annevk Jan 9, 2023
09074df
say quite a bit more about limits
annevk Jan 10, 2023
f971dee
Update infra.bs
annevk Jan 11, 2023
9f883f8
final review nits + my own
annevk Jan 11, 2023
b8e8f5a
nit + acks
annevk Jan 12, 2023
c645968
reword the end
annevk Jan 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions infra.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,6 +239,13 @@ paths would be an insurmountable task and not productive as they would not stand
as well as the single algorithm would. Therefore performance is best left as a field to compete
over.

annevk marked this conversation as resolved.
Show resolved Hide resolved
<p tracking-vector>A document using the Infra Standard should not enforce specific limits on
annevk marked this conversation as resolved.
Show resolved Hide resolved
unconstrained inputs to allow for competition among user agents and foster ever greater data
annevk marked this conversation as resolved.
Show resolved Hide resolved
annevk marked this conversation as resolved.
Show resolved Hide resolved
structures over time. I.e., avoid constraining the computing needs of the future. Nevertheless, user
agents may impose <a>implementation-defined</a> limits on otherwise unconstrained inputs. E.g., to
prevent denial of service attacks, to guard against running out of memory, or to work around
platform-specific limitations.


<h3 id=algorithm-declaration>Declaration</h3>

Expand Down Expand Up @@ -1995,6 +2002,7 @@ Chris Rebert,
Daniel Ehrenberg,
Dominic Farolino,
Gabriel Pivovarov,
Ian Hickson,
Jake Archibald,
Jeff Hodges,
Jungkee Song,
Expand Down