I found the solutuion.
Chrome shows the loading indicator if connection was made immediately
from the "body onload()", i.e. from onModuleLoad().
Do not connect to the server immediately but schedule a timer and
connect after a second or more.
This works for me:
Timer timer = new Timer() {
@Override
public void run() {
connect(sessionId, cometCallback);
}
};
timer.schedule(1000);
It seems that the pause shouldn't be too small. 1 sec seems to be
enough, but it should be checked on slow machines too.
On 11 дек, 19:44, Andrey <[email protected]> wrote:
> Hello!
>
> I am using comet (server push) in my application. When user logs in a
> secondary connection being created. It is an ordinary GWT RPC call
> with 50 sec timeout and retry.
>
> Everything is OK except that Chrome and the Chrome only shows loading
> indicator as if the page is loading.
> How can I get rid of it?
>
> Thanks in advance!
--
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.
