It's not that simple. The user can return to the same place many times over the course of the application. Each time they go place X, there may be a different number of objects that they loaded while they were at Place X.
My idea was to just update the current place (which is the same instance the entire time they are at Place X, until they leave and go somewhere else) with the max results each time new data is loaded. That way, the FINAL state of the place is stored for if they navigate back to it with the history mechanism. Trying to use localStorage doesn't work because each INSTANCE of the place doesn't have anything unique about it that I can use as a sort of map key, right? -- 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.
