On Wed, Jan 14, 2009 at 3:28 AM, Thomas Broyer <[email protected]> wrote: > On 9 jan, 20:11, "Ian Petersen" <[email protected]> wrote: >> Threading will not be >> supported in GWT for a long time to come simply because the majors >> browsers won't support threaded Javascript for a long time to come. > > Well, that's not really true... > Gears brings "web workers" (aka "web work threads") to supported > browsers, and the next versions of Firefox and Safari (I don't know > about Opera and IE) will have them natively (as defined in > http://www.whatwg.org/ww > ). > (Chrome embedding Gears, it already had them natively since the very > first beta ;-) ) > > Not multi-threading the way you usually think of it from a developer > point of view but still.
I'd forgotten about that but, now that you mention it, aren't Gears threads more like processes? A quick read through the very intereting spec you linked to suggests that you can only send strings between threads. Importantly, this means you can't share references across threads, and ThreadLocal is still "redundant". I guess what I'm saying is, I was wrong--threading _is_ available in the browser--but I think my point stands: Java-style threads still seem to be beyond the horizon. Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
