On Monday, May 23, 2011 11:34:31 AM UTC+2, ra wrote: > > Hi, > > > I recently tried to use GWT's Cross Site linkers to allow GWT code > loaded from different servers. > And - they really like a charm - great work! :) > > Linker "xs" does not seem to work in dev mode [1], Linker "xsiframe" > [2] works both in dev an production mode, but needs script tags of > gwt.xml to be included by the host html page. Both seem to support > code splitting. > > But still - can anybody explain why there are two Cross Site linkers? >
"xs" is the "historic" one, and will probably be "deprecated" at some point; xsiframe has been added quite recently. I even heard "xsiframe" would replace (read: be preferred to, and used by default) "std" in due time. > What's the difference between the two? > As its name suggests, xsiframe runs the code in a iframe "sandbox", just like the "std" linker. But contrary to the "std" linker, it loads the code using dynamic script tags, which allow for cross-origin uses. On the other hand, the "xs" linker runs the code "in the host page", using the "module pattern" to avoid polluting the global context, but still running in that global context, and thus subject to "pollution" and side effects from 3rd party libs. This is just the general idea, I don't know the exact details of how xsiframe is better than xs (just that it must be, otherwise they wouldn't have created it afterwards) -- 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.
