When using activities and places, what is a proper approach to passing data 
through places on link clicks, but still keeping the good behavior 
associated with "real" links.

Is it best to use an Anchor, set an href using the placeHistoryMapper, and 
then preventDefault on the DOM when the anchor is clicked? That way, we 
still operate on the actual Place (which would contain some data, 
conceivably) unless the user directly navigates to that link in the URL bar 
or does a right-click -> Open in...

Or is it best to encode only the data necessary in the Place token and 
fetch what is required from the server based on that "shallow" Place?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/uPNEp55ycDUJ.
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.

Reply via email to