@zixzigma: stateful in the sense that the view (or the presenter if you're using MVP) has a private variable that keeps the last page seen and is only initialized on a new search. As a consequence, it would show the exact same page if you navigate back to it.
On Feb 4, 2:08 pm, Jason <[email protected]> wrote: > Good suggestions, the reason that I've been using the URL to rewrite > the list page parameters (rather than having a stateful page) is that > I'm using it for both paging and the query parameters. For example, > if the user is searching for customers where the name starts with > 'ABC' then the URL is rewritten as something like > 'list#customerNameStartsWith=ABC&page=2'. This allows the user to > easily bookmark a query or page of results. You could still use the stateful view approach with the query string in the URL, letting the user bookmark the query. With that approach, the only thing you can't do is let him bookmark the page number. IMHO bookmarking a page often does not make sense, especially if you have a dynamic database where the search results change through time. -- 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.
