That's why we introduced packaged resources in the first place: to
have static urls. If you don't have static urls, your browser
shouldn't cache them. Don't we set expiry headers?

Eelco

On 10/1/05, Gili <[EMAIL PROTECTED]> wrote:
> Hi,
>
>         I'm using PageableGridDataView to display a grid of images. Here is an
> example URL for a thumbnail on a page:
>
> http://localhost:8084/DesktopBeautifierServer/Main?path=11:imageRow:1:cols:4:imageWidth:imageLink:image&interface=IResourceListener
>
>         The problem is that upon server restart the path counter resets. Now,
> if a user hits the image listing again, his browser recognizes the
> original URL and uses the cached image. However, path=11 in the new
> server instance does not equal to path=11 in the old server instance, so
> the cached image is incorrect.
>
>         Is there a way for us to serialize the "path" values on shutdown and
> pick them up on restart? This will ensure the browser cache doesn't
> display incorrect images. I don't mind if users can't hit older pages
> (i.e. path=10 and below) because they don't exist in the new server
> instance but at least the counter should begin at the last used value +1
>
>         Let me know what you think.
>
> Thanks,
> Gili
> --
> http://www.desktopbeautifier.com/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to