- From: Glenn Maynard <glenn@zewt.org>
- Date: Fri, 7 Jan 2011 00:01:08 -0500
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: João Eiras <joao.eiras@gmail.com>, public-webapps WG <public-webapps@w3.org>
2011/1/6 Boris Zbarsky <bzbarsky@mit.edu>: >> since it runs scripts in their own thread. > > No, it doesn't. Shrug--it's something mentioned in Chrome-related tech talks, whether it actually, or still, does or not. It certainly runs scripts concurrently with each other, and without blocking the containing window, which is the point. >> I can only hope that all other major browsers will >> do that eventually > > IE8 and Chrome have pretty similar process-per-tab-like architectures, for > what it's worth. Which has nothing to do with threads. Processes have quite a lot to do with threads. The distinction isn't very important to the discussion, since writes to localStorage are visible across tabs whether they're running in the same memory space or not. -- Glenn Maynard
Received on Friday, 7 January 2011 05:02:26 UTC