On 9/24/2014 9:26 AM, Martijn Dashorst wrote:
On Wed, Sep 24, 2014 at 2:13 AM, Garret Wilson <gar...@globalmentor.com> wrote:
I'm not denying that versioned pages may be a useful concept for some use
cases (even though I can't think of any offhand).
Persioning is a very useful concept and used in many applications. You
are just focussing on your particular use case for today and not
thinking of broader issues that we have tackled for about a decade.
Take google's search page with the pagination at the bottom. Click on
2, click on back. What do you expect? go back to the page before you
searched google? Or go back to page 1?
But note that in your example you're not talking about the "version of
the page". You're pointing to a /navigation control/, which of course I
would expect to interact with navigation. Notice that when you page back
and forth, you actually change the URL query (e.g. start=10). So you're
not changing the "version" of the page---you're actually modifying the
query you send to the page, and of course you can navigate among
different page queries. In fact Wicket already has a totally separate
mechanism for sending queries to pages through page parameters, exactly
like Google is doing.
I am completely in favor of sending page query parameters in the URL
when I want to specify what data should be retrieved from a query, and
for the user to navigate among queries. But I still (in my use case)
don't have a need for that same query page to be "versioned".
Garret
