If you really want to stick with the client side and want to have an async-like experience you could also use a Timer to trigger the search. Schedule the Timer as soon as the user begins to enter his search and cancel + re-schedule it on every key hit. This way the blocking search will only start as soon as the user has stopped typing for a specific amount of time. You will have to try and check what is a reasonable schedule time. This should work I think.
On 18 Nov., 15:09, MickeyR <mnroo...@gmail.com> wrote: > Is there anything similar to using java threads that I can use in myclient > sidecode ? > > In my application a user types a search term into a Text box. For > every character typed in my code goes and searches in a dataset for > results containing the search string. These results are then returned > and displayed in a List. But the problem is that because my search + > display code is so slow, it makes the typing in very sluggish for the > user (i.e. they can’t type the next character in until the search + > display code has returned). > > Ideally I’d like to run the search+display code in a separatethread– > so that the user can continue to type in the Text box. But I > understand that threads are not supported inGWTclient-sidecoding ? > Or is it possible to have the search + display in an > onlyclient-sideasynchronouscall? > > Any help, much appreciated, > M. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
