Sunday, February 26, 2012

Re: Timer AsyncCallback issue

I think your issue might be that you are getting a lot of data back in
your RPC call and the browser is frozen while it is processing the
results. If this is the case maybe you should either send a smaller
amount of data to the browser (maybe break up the RPC request into
multiple smaller ones) or consider using Request Factory to transfer
the data as that is better able to keep the browser from freezing with
a bigger payload.

On Feb 24, 3:43 pm, "Peter D." <> wrote:
> I have a timer set up to update an element on my UI periodically from
> a buffer.  If the buffer grows too small, I make an RPC call which
> returns the next chunk of frames.  However, I want the timer to
> continue updating the UI off the existing buffer while the RPC call is
> working.  It seems that when the buffer needs to grow, the timer calls
> calls the AsyncCallback function correctly and continues through the
> rest of the run() function, but the next scheduled execution will not
> occur until after the RPC call returns.  Is there any way around this?

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

No comments:

Post a Comment