- From: <bugzilla@jessica.w3.org>
- Date: Wed, 13 Oct 2010 17:43:33 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10801
Maciej Stachowiak <mjs@apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjs@apple.com
--- Comment #4 from Maciej Stachowiak <mjs@apple.com> 2010-10-13 17:43:31 UTC ---
I think defining limits is a good idea. It's true that hardware gets faster
over time. However, if neither loop of the AAA is limited, there is content
that will take quadratic time to parse proportional to its size and may hang
the parser. This has a few consequences:
1) It's not sufficiently Web-compatible to implement AAA with no limits; there
will be occasional pages that hang for minutes at a time.
2) Faster hardware will not allow the limits to be substantially increased,
because of the quadratic growth problem. There will always be plausible-sized
pages that can cause a hang at higher limits.
Since browsers have to have limits and will likely need them indefinitely, it's
better for long-term interop if browsers agree on the limits and if the spec
reflects that agreement. Since it's unlikely the limits can be increased a
great deal, and since raising them quickly runs into diminishing returns as far
as better compatibility goes, it is not very helpful to retain the freedom to
raise the limits later.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 13 October 2010 17:43:34 UTC