A co-worker and I are looking into how to provide a consistent
handling of session expiration with an AuthenticatedWebApplication.
If a session expires, ideally, we'd like to provide a consistent
behavior of redirecting to a login page with a helpful message (i.e. -
Your session expired, please
Hello I've been using wicket for almost a year. I recently ran into the
common web problem of the browser being overly aggressive on caching
javascript files. This is commonly solved by adding a query parm which
changes based on the contents of the js file (checksum, time-stamp, etc).
After
Matej,
A parameter on the url seems like a small price to pay to guarantee that the
client has the correct version of the resource (IMHO). There are other
frameworks which do similar things by default. Is the only reason not to do
it that the url looks a little less clean?
- Matt
p.s. - The
