HTML5 now has a "storage mutex" concept to cope with cookies being set in a multiprocess UA architecture without having scripts be exposed to race conditions.
This affects XHR in a couple of ways. For both sync and async XHR, we should add a must-level requirement that UAs are to "obtain the storage mutex" (term of art defined in HTML5) before setting cookies. For sync XHR, we should add a must-level requirement that UAs are to "release the storage mutex" (storage mutex is a term of art defined in HTML5) at the start of the sync process and again immediately after setting cookies. Cheers, -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
