On Dec 11, 2007, at 11:22 AM, Aaron Boodman wrote:
How does the globalStorage implementation deal with this problem? It has a synchronous storage API. True it is probably designed for smaller amounts of data, but there's nothing preventing an author from using it for large amounts (is there?). Also, some of the concerns raised here have nothing to do with the amount of data stored. Or does globalStorage not guarantee that data is written when the setter returns?
I see nothing in the globalStorage spec that suggests that the data must be on the disk by the time setItem() returns, and I think it would be crazy for a user agent to voluntarily store the data out to disk before returning from the method.
~Brady
