On Sep 17, 4:13 pm, Johannes Lehmann <[email protected]> wrote: > OK, that is basically what I assumed. This however seems to create > concurrency issues, which the synchronized keyword was designed to > address. Without any language support such as semaphores or mutexes > and without any guarantees regarding preemption, how could I solve a > problem such as the above?
Excuse my ignorance about semaphores/mutexes/preemption details, but how can there be concurrency issues if things never execute concurrently? (and *your* code will never execute concurrently with *your* code) If you really want the gory details: http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#event-loops -- 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.
