This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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
I'll take this bug and make this small change, adding the recommended text.
Added this sentence: User agents need to ensure a reasonable level of fairness across readers and writers to prevent starvation. (In the check-in, I accidentally wrote, "per bug 10381" rather than "per bug 10382". Apologies for any confusion.)