> Here's how I'd like it to work: > > User enters a URL: new token is removed from the current history > without reloading elements on the page, token is evaluated by the > developer's StateHandler's validateToken() method, and > ClientHistoryHandler.update() is called with a proper token. > User hits back or forward or triggers a change through page > interaction (button, link, etc): token is assumed to be correct and > ClientHistoryHandler.update() is called immediately. >
Actually, that's not quite right... Here's what I'd like it to do: User enters a URL: calls History.back(), which isn't handled, followed by the API developer's validateToken() method, which then calls ClientHistoryHandler.update() with the appropriate new token User triggers a change through page interaction (button, link, etc.): token is assumed to be correct and ClientHistoryHandler.update() is called immediately. User hits back or forward button: all of the ClientHistoryHandler's onValueChanged methods are executed as if update() had been called. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
