A html or jsp file is used to launch the xxx.nocache.js, which then
decides which browser "permutation" to use.
<head>
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<title>xxx</title>
<script type="text/javascript" language="javascript"
src="xxx.nocache.js"></script>
</head>
In my case, I am using a jsp. When the JSP is executed, it discovers
some conditions. I wish to pass these conditions as variables to the
GWT generated javascript being launched. The "elegant" GWT way to pass
these conditions would be to persist those conditional values as
request/memcache attributes and then have the GWT module perform RPC
to retrieve those values.
But why should I have to do that. For example, the JSP discovers that
the current user is Whoopy. Shouldn't I simply have the JSP generate
javascript to store
user = "Whoopy"
as a top level javascript variable and use JSNI within the module to
retrieve the value for user?
I would like to have suggestions on how anyone is performing such
communication to escape from having to maintain a request attribute
and a subsequent RPC.
My problem arises further when the launcher sits on another Iframe/
frame, so I should need to take note of the name of that frame from
which the module is being launched.
I have not tried it (launcher-to-module communication) yet so I do not
know if it would work. Any suggestions is greatly appreciated.
--
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.
