Sorry, the alternative below would be to have the URL contain enough information about the new "place" (such as an ID if that's sufficient to get all the data we need) and then always populate from scratch. I would call that a shallow place - it doesn't contain all the data we need, but it contains enough data to go fetch it.
On Thu, May 17, 2012 at 6:14 AM, Thomas Broyer <[email protected]> wrote: > > > On Tuesday, May 15, 2012 10:13:56 PM UTC+2, Shaun Tarves wrote: >> >> 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... >> > > Yes. > > (though I actually didn't understand the alternative below ;-) ) > > >> >> 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/-/UdwC9D_-OuoJ. > > 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. > -- 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.
