> > 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... >
IMHO then I would try to encode "last revenues in 3 years" and not the state of all checkboxes. In general I tend avoid storing UI state in the URL that directly maps to a UI component state because if you refactor the UI in the future these links are likely to become invalid. So I try to store a meaningful abstraction of the concrete UI component state. So given the above example my URL would look like example.com/#SomePlace:revenuesSince=<milliseconds to substract from today> or something like that -- 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.
