the checkbox info is not too important to a level that I need to store them into DB. For example, 3 checkboxes were checked to show the last revenues in 3 years... If the check boxes were not checked then user can still figure out & can check by themselves. But if the url can tell exactly which checkboxes were checked then the user experience is a little better but not the most necessary.
On Friday, June 6, 2014 7:58:45 PM UTC+10, Jens wrote: > > let imagine this app, u have a page that have lot of checkboxes & users >> may click 5,10 or more checkboxes randomly, & last time when user visit the >> page they should be able to see exactly the number checkboxed that was >> checked in the exact locations that they did last time. For example, user >> select 10 checkboxes in an url & 10 years later if they visit the same url >> they still can be able to see 10 checkboxed were checked at the exact >> positions that the user set 10 years ago. There is no way to use session or >> state objects in the situation like that. >> > > Well then you have to store it into the DB. Honestly I can not imagine why > you should not save it to DB as these checkbox selections seem to have a > meaning important to you and you don't want to loose that selection. > > When you store it in a DB then your URL would just have a (possibly > encrypted) Database ID that allows you to fetch the information when you > load the URL fresh. > > -- J. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
