GWT's History mechanism allows you to interact with the browser's history stack.
GWT applications as ajax-applications do not interact with the browser by default in the same way as static web pages. History mechanism in GWT makes history support fairly straightforward.
GWT's History mechanism has a lot in common with other Ajax history implementations, such as RSH. The basic premise is to keep track of the application's "internal state" in the url fragment identifier. This works because updating the fragment doesn't typically cause the page to be reloaded.
This approach has several benefits:
- It's about the only way to control the browser's history reliably.
- It provides good feedback to the user.
- It's "bookmarkable". I.e., the user can create a bookmark to the current state and save it, email it, et cetera.