There is just 1 JS thread. Regardless of URL or IFrame. The limit of max 2 connections is purely based on URL, not on per IFrame basis. IE8 allows more than 2, I forgot the exact number. To work around the connections limit you can spread web resources over different hosts in the same domain.
Getting access to static classes in different IFrames can works but: 1) security restrictions might stop you from calling from one IFrame to another. 2) GWT code is obfuscated and can be totally different with every change you make. So in order to get access to some static classes, you will need to expose them through JSNI. On Thu, Sep 3, 2009 at 2:10 AM, ben fenster<fenster....@gmail.com> wrote: > > another thing about the http request limitation most browsers rejects > more then 2 simultinus requests to a spacific url and i wondered i > its aplays to 2 diffrent browser windows (diffrent process in new > browsers) and if iframe acts as new web page maybe the limitation > grows by 2 for each iframe > > On Sep 2, 5:05 pm, ben fenster <fenster....@gmail.com> wrote: >> your answear is based on your knolage in js but i need an answear >> based on actual in depth knowlage in how browser work since each >> iframe act as an independed wep page and loaded sepertly then the >> containing page made me wonder about how its being done without a >> diffrent thread ? >> and if another thread is envolved in loading then maybe the new thread >> is also responsible on running the js code contained in the page of >> the iframe ? >> On Sep 2, 5:46 pm, David Given <d...@cowlark.com> wrote: >> >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> >> > ben fenster wrote: >> > > i was wondering that if by opening another module in an iframe tag the >> > > code of that module runs in another thread ?? >> >> > Nope. There is no way of getting access to multiple Javascript threads >> > from a web browser, unless you use some sort of extension like Google >> > Gears or HTML5 web workers. Every part of the Javascript VM that your >> > code can see is part of the same event loop. >> >> > > more over is the limit of 2 open http request apply on 2 diffrent >> > > modules running in diffrent iframes ?? >> >> > Don't know about this one. >> >> > - -- >> > ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─────http://www.cowlark.com───── >> > │ >> > │ "People who think they know everything really annoy those of us who >> > │ know we don't." --- Bjarne Stroustrup >> > -----BEGIN PGP SIGNATURE----- >> > Version: GnuPG v1.4.9 (GNU/Linux) >> > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/ >> >> > iD8DBQFKnxH6f9E0noFvlzgRApqiAKC/xF4z1x0t7s+8kAsTVoSxYFRFmQCfaUcx >> > 7F+QaH0Fdc9baW9Wcgl3swM= >> > =ukVk >> > -----END PGP SIGNATURE----- > > > --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
