Re: History mechanism

The URL token can also refer to an object that captures state locally
on the client. I do this as I have no simple state token which can
represent what is showing on the screen. This works great for
history, however the link is of course not transferable to another
browser session. For that, even if you could squeeze the actual state
into the url, you probably wouldn't want people trying to cut&paste
multi-kb urls to each other! And it doesn't make sense to capture
every state change and send it to the server just in case someone
wants to send the link to a friend. Instead, I do something similar
to Google maps, which is a specific link/embed button which stores the
current state to the server and creates a unique token, and presents
that link to the user to copy/paste.

On May 23, 10:46 am, Stefan Bachert <stefanbach...@yahoo.de> wrote:
> Hi,
>
> the history mechanism is based on urls.
> Urls are limited. My memory says 2KByte is the limit of an url.
> This implies, that the GUI-state may not exceed this limit, too.
>
> Do you agree with this?
>
> Stefan Bacherthttp://gwtworld.de

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.