path=x is used for pages not resources. in any case the trick is to simply append the jsession id to a stable url. that way the url stays stable within the session.

something that normally would be accessed as /app/resources/image/45
wher 45 is the id of the image
would not be accessed as

/app/resources/45/sessionid

you just have to appen the session id whenever you are building the url.

-Igor



On 1/25/06, Gili <[EMAIL PROTECTED]> wrote:
Hi,

        I've got images with non-bookmarkable URLs (I specifically don't want
them to be bookmarkable) and Wicket assigns them path=X where X is some
number. Now, it seems that path=X is session-bound, which means that X
is reset to 0 every time the client browser is restarted.

        The undesired side-effect is that path=0 might map to different images
on every browser restart but the browser seems the same URL so it
assumes the image might be the same and it dishes out stale images from
its cache.

        I could set the "no-cache" header on the image but this isn't exactly
what I'd like to do (since refreshing the same image within the same
session should not cause it to be re-downloaded from the server).

        Is there a way to tell Wicket to keep on incrementing X across sessions
or otherwise guarantee correct behavior? almaw mentioned on IRC I could
map the images to http://foo/yourUniquePerSessionIdHere/content which
might solve the problem but I'm not sure how to do this.

Thank you,
Gili


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to