You could use Google Gears (already included in Chrome), http://code.google.com/apis/gears/api_workerpool.html
On Sat, Mar 28, 2009 at 2:48 PM, ell.mdnttech <[email protected]> wrote: > > In some ways I agree but having multiple processes would allow it. > And there are ways of limiting the number of threads available. > Looking at the zero-rights processes in Chrome there's little reason > that it would be a threat to the OS either as the threads would be > sandboxed as well. > > On Mar 28, 6:16 pm, Jarrett Wold <[email protected]> wrote: >> I would think that allowing javascript to spawn threads would be a >> nightmare. >> >> On Mar 27, 7:27 pm, "ell.mdnttech" <[email protected]> >> wrote: >> >> >> >> > Just an idea, but it came to me the other day that chrome's multi- >> > process architecture could open up threading for web applications. It >> > could be as simple as a javascript call that executes a method on a >> > separate thread. Web apps are persistently catching up with desktop >> > and this could be another step in the right direction. >> >> > Any thoughts? > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
