That technique is workable, but a bit cumbersome in my use case. When
a user first navigates to a Dashboard page, the URI pulled would not
include the nonce parameter. Easy enough to have the 'refresh now'
command add the nonce.
However, the user will typically drill down to another page, leaving
the Dashboard page, only to return to the Dashboard page shortly
thereafter. At this point, the Dashboard page will load the 'default'
URI (without the nonce parameter).
So, I'd need to modify the control to track the 'nonce' URI across
page views (e.g. put it in a cookie; if the cookie exists, use it,
else use the 'default' URI). Certainly doable.
However, I was hoping for a slick version along the lines of new
Location(default URI).reload().
Thanks for the feedback!
Eric
On Jul 14, 3:04 am, Sean McArthur <
sean.mons...@gmail.com> wrote:
> Whenever I wish to break cache, I include a nonce GET parameter.
>
> '&nonce=' + (new Date()).getTime()