I wouldn't use queries that have as parameter the user's ID receiverd from the client because that could cause a security issue (let's say a hack could change the id that will reach the server). Instead you could store the user's ID on server side based on the current session (which probably depends on your server side technology). So then you would pass the stored value of the ID to your query. But the use of the stored account id on client side is ok if you use it for graphical purposes (widget view customization let's say...).
On Jul 29, 3:46 am, Ho Jimmy <[email protected]> wrote: > Hi, > > This is a application design question with GWT. > After the user login, the application needs to load widgets with user > specific data. > I maintain a base panel with a private variable, accountId. After the user > login, it will assigned the account id to this private variable. > Then, the widgets added to the base panel will use the accountId to query > the database by RPC. > So, everytime I need to check the accountId when I need to load new widgets, > and it would be redundant if I have a few base panels. > > Is there any other suggestion? > > Thanks > Jimmy -- 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.
