Hi Chii, Thank you for your suggestion Why client side solution is not secure? Because in JSP the presentation logic was hidden in server. And if I pass all the parameters to GWT via JavaScript, everyone can play with it by changing HTML source.
On Jan 11, 2:34 pm, Chii <[email protected]> wrote: > Why is it not "secure" to pass parameters from client side (whatever > that actually means...)? > > I say the second method of defining a GWT Dictionary in JSP is the > easiest way. Or, instead of GWT Dictionary, use javascript overlays: > define a custom javascript object in the page, and access it through > javascript overlays. Advantage is type safety, and autocomplete. > > ~Chii > > On Jan 11, 4:31 am, wera <[email protected]> wrote: > > > Hi All, > > > I am adding a GWT component in JSP. It should receive several > > parameters to know how to present data (for example, how many buttons > > should be, what is the selected value in a drop-down, etc.) > > > The question is how to pass parameters from JSP to GWT. > > > I saw several ways to do it: > > 1) Go to server, for example using RPC (I prefer not doing this - to > > save time and minimize number of requests to server) > > > 2) Pass parameters from client side (might be not secure). I saw 2 > > ways: > > -define in JSP a GWT Dictionary to contain a map of values that GWT > > component needs > > -add parameters on request - in include of GWT noscript.js > > > What is the best practice? > > > thanx --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
