I'm trying to use reverse ajax to publish online events to a web browser.
Everything works fine with firefox.
In ie6, I get a low update rate.
The update period is equal to the parameter I set in "maxWaitAfterWrite" (if I
set 5000, the values are updated once every 5 seconds).
This
is because Firefox's and IE's XHR implementations behave differently; the
Firefox XHR supports streaming which lets HTTP response data become available
before the request is closed. In IE it only becomes available after the request
is closed.
The
maxWaitAfterWrite parameter determines how long after writing response data
before the request is closed, and it is thus not until then that the data
will become available in IE.
Setting a lower value increase the update rate but then I get a "memory
hog", memory consumption of ie grows very fast until I minimize the window
(very strange behaviour).
We
have fixed a number of memory leaks in 2.0.4 so could you please check with the
RC again? You may also want to try, and compare with, DWR's Reverse Ajax
Clock example that have been verified not to leak.
Best
regards
Mike
Wilson
