+++ Andrew MacKenzie [wicket-users] [Tue, Nov 13, 2007 at 11:45:46AM -0500]: > Well, I've got it up and running, but it appears that Wicket is caching > 'something' because it is only requesting the content once (the first time > it's hit). Even if the requests come from different browsers.
I've been digging a bit more - looks like wicket *does* cache things, and polls at configurable intervals to determine whether the resource has changed. For me this is less than ideal.. I had assumed that every request to wicket for a resource would result in my AbstractResourceStream being invoked for the body. My problem is that my ResourceStream is similar to wicket.util.resource.UrlResourceStream only it also sends along cookie information. This is because the remote resource will be different for each user (will display the user's login name). If this is cached at all there is a possibility of another user seeing the wrong content. I can minimize this by making the polling interval very short, but there is always the possibility. Can I tell wicket to ignore the polling and always query the resource for the content? -- // Andrew MacKenzie | http://www.edespot.com // GPG public key: http://www.edespot.com/~amackenz/public.key // Persons attempting to find a motive in this narrative will be prosecuted; // persons attempting to find a moral in it will be banished; persons attempting // to find a plot in it will be shot. By Order of the Author // -- Mark Twain, "Tom Sawyer"
pgpP616PS3cIO.pgp
Description: PGP signature
