It can be done client side as a previous poster said using a timer with a callback but first he should run Speed Tracer to determine why the code he has now is bogging down the client.
Jeff On Thu, Nov 18, 2010 at 12:23 PM, bjv <[email protected]> wrote: > On Nov 18, 8:09 am, MickeyR <[email protected]> wrote: > > Is there anything similar to using java threads that I can use in my > > client side code ? > > I can't think of any portable ways to do this. The only way you can > get the behavior you want that I can think of is to create a browser > plugin (like a firefox protocol handler) that you can issue gwt's > async requests to. In essence, the local plugin looks like a remote > site to your application. It will look like an ajax type request from > your gwt code's perspective, however the handling of the search > request/etc will all run in the plug-in/protocol handler. And of > course, if you are loading your app from a server somewhere, you'll > have the browser's same origin policy issues that you will have to > solve (unless you load your gwt app from your plugin as well). > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- *Jeff Schwartz* -- 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.
