http://www.w3.org/Bugs/Public/show_bug.cgi?id=10382
Summary: [IndexedDB] Note on avoiding reader/writer starvation
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Indexed Database API
AssignedTo: nikunj.me...@oracle.com
ReportedBy: pablo.cas...@microsoft.com
QAContact: member-webapi-...@w3.org
CC: m...@w3.org, public-webapps@w3.org
Since in locking-based implementations it's going to be relatively easy to get
into a situation where readers starve writers when working concurrently, we
should have a note in the transactions section that encourages implementations
to have explicit mechanisms to avoid starvation. We don't want to be too
prescriptive, perhaps simply this statement:
"UAs need to ensure a reasonable level of fairness across readers and writers
to prevent starvation."
For reference, we discussed this here:
http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0504.html
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
