Browsers run javascript in a single thread. This means you do not have to worry about concurrency at all, and you can't do any sort of multi-threaded worker type stuff in GWT (which is a client-side technology). The server can do whatever you want though.
Ståle Undheim wrote: > I wish to create a request que, where data that needs to be fetched is > submitted to a service, and then 1 request at the time is executed. I > am wondering if someone has allready made something like this that I > can use, or rip off. Basically I want an API where you submit a job, > and a callback for when the job is done. When a job is added, it needs > to be put in a que. And a when a job is done, the next job in the que > needs to be executed. > > My worry here is in regards to concurrency. When a job is submitted, > the state can either be that a job is beeing executed, or there is no > job running, as well as the que might be empty or not. If the que is > non-empty, I just append the job to the end. However, if the job is > empty, I need to be able to check if there is allready a job running > or not. If there is no job running, I can safely execute the job. If > there is, it will get executed when the current job is done. > > Do I need to worry about concurrency in GWT? Are there any worker like > libraries for use with GWT? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
