I tried many tricks as they were implemented in jQuery and other JS toolkits but none seem to fully solve the issue completely. I've implemented a caching strategy and now I avoid doing the same jsonp call. The data I am returning allows this since it is a finit set.
But I do hope I can come up with a total solution.
The IFrame leak was mainly caused by GWT not detaching the Ui in the onclose handler. That is a bug in IE and GWT does not support unloading on demand. But a fix is int the pipeline.
If you find a generic solution to the jsonp leak please let me know! I rather let the browser handle cash operations.
David
On Thursday, January 3, 2013, Matthias Kühnle wrote:
-- On Thursday, January 3, 2013, Matthias Kühnle wrote:
I experienced the same bug. Did you solve your Problem somehow?Matthias--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Z5eNy9RMEpEJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment