Hi Sefan, Many thanks for your clarification. Appreciate it. May I ask what is the difference between GWT-RPC and GWT?
So this means that the data cache at client side can be controlled right? Thanks once again. On Jul 28, 3:26 am, Stefan Bachert <stefanbach...@yahoo.de> wrote: > Hi, > > GWT is putting javascript into the browser cache. > Data which are coming from GWT-RPC do not went into the browser cache. > > However, a client data cache (programmed in java/javascript) greatly > improves the data loading by avoiding duplicate requests. > I do not see a security hit from doing so. > Even a browser cache is no security hit as long the user account of > the operating system is not shared. > > Stefan Bachert > http::/gwtworld.de > > Inquiries for professional GWT support are welcome. > I am sorry, I won't do free personal support. > > On 27 Jul., 09:08, Joyce <joyc...@gmail.com> wrote: > > > > > Hi. I believe that GWT achieves RIA through initial throwing of > > objects and files to the client side initially. but what I do not > > understand is that is it possible to control the amount of information > > being thrown to the client side? cos this is because I do not want > > sensitive information to be cache at the client side. these > > information shall only be retrieved from server when requested. > > > these information should only be sent to the client only when > > requested and should not be cached at the client side. does anyone > > know if it is possible to control the amount of information being sent > > to the client? can anyone enlighten me? would appreciate your help > > sincerely. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
