Allahbaksh,
Ray hinted at a 'Place' abstraction in the last few minutes of his I/O talk:
http://code.google.com/events/io/sessions/GoogleWebToolkitBestPractices.html
While there's no source code for this, you can get an idea of how this works
by his description.
In general I'd recommend uses history token in a few cases:
1. Application state which you'd like to be bookmarkable, e.g. 'currently
viewing account for customer number 42'
2. Application state which you'd like to (at least partially) survive a
full page refresh (or a browser crash + recovery :)
3. Application state you want to be accessible from the browser 'back'
and 'forward' buttons
HTH
Fred
On Tue, Jul 7, 2009 at 1:33 AM, Allahbaksh a.allahba...@gmail.com wrote:
Hi,
Is there any best practices or design for implementing History in an
application.
Regards,
Allahbaksh
--
Fred Sauer
f...@allen-sauer.com
--~--~-~--~~~---~--~~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
