I thought so :). There's no concurrency in Javascript. There's no light without a bulb. Viliam
On 13. Jan, 14:39 h., MikeN <[email protected]> wrote: > Ok, ignore this... bug was on my end. > > Apparently someone decided it was wise to use an instance variable in > the service class to build the resultset. Of course requests get > handled concurrently on the serverside, so I had a threading issue > there. Fixed by using a method variable. > > Thanks for the replies all. > > --Mike > > On Jan 13, 2:26 pm, MikeN <[email protected]> wrote: > > > On Jan 13, 8:22 am, Viliam Durina <[email protected]> wrote: > > > > Do you use DeferredCommand? This way, onSuccess can execute before the > > > DeferredCommand is executed. > > > No, I don't use deferred command. > > > > On 13. Jan, 05:22 h., Isaac Truett <[email protected]> wrote: > > > > Are you sure the responses are being handled concurrently? JS is > > > > indeed single threaded, so you should be seeing those responses > > > > handled sequentially, although the order in which the requests will > > > > return is not guaranteed. > > > Quite sure they're being handled concurrently, don't have any other > > explanation as to why I get duplicate items in my list. > > > > > Based on your description, I would suggest disabling the button after > > > > sending the request. In both onSuccess() and onFailure() you can > > > > re-enable the button. > > > Yeah, but the problem is it's not 1 button, the complete scenario is > > somewhat more difficult to explain. I'll try to come up with a small > > testcase. > > > --Mike
-- 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.
