On Sunday, March 4, 2012 8:07:54 PM UTC+1, dhoffer wrote:
>
> Thomas,
>
> Thanks for the info...gwtjsonrpc looks especially interesting.
>
> However these solutions seem to be at the RPC level...e.g. to allow
> cross site RPC calls. What about the GWT UI? How does the GWT UI get
> mashed with the host site? Seems like the GWT war would have to be
> split with its client code still hosted by the main hosting site?
> Maybe I'm missing something here? Can someone elaborate how this type
> of thing would get deployed? The goal is to keep all of the GWT war
> remote...as much as possible.
>
The UI is built by your *.nocache.js and *.cache.* scripts. If you use the
xsiframe linker, you can load the code from whatever server and it'll "just
work".
Integrating into a non-empty HTML page is as easy as using
RootPanel.get("some-element-id") as the root(s) for your UI.
What about CORS...does that help?
That'd help for communicating with your server (RPC), without the need for
JSON-P or similar, but obviously won't work with IE (until IE10 is
widespread).
--
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/-/4LmXbx4ojpkJ.
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.
