wicket doesn't do the caching of the result of the AbstractResourceStream Wicket only passes that lastmodifiedtime to the browser, which should on his turn do the caching.
So if you are sure that your stuff doesn't have to be updated a lot then you should cache it For every different client/browser we will call the data. johan On 11/5/07, Andrew MacKenzie <[EMAIL PROTECTED]> wrote: > > Wicket 1.2 > > > I've created my own implmentation of AbstractResourceStream to fetch the > content for some pages from another location (they are generated by > another > site). > > One thing I'm not sure of is how often wicket will re-fetch this resource > from my code. I notice a "lastModifiedTime()" function I have to > implement, and I wonder if wicket uses that to determine a timeout? Does > wicket do caching here or should I? > > -- > // Andrew MacKenzie | http://www.edespot.com > // GPG public key: http://www.edespot.com/~amackenz/public.key > // "If my theory of relativity is proven successful, Germany will claim > // me as a German and France will declare that I am a citizen of the > // world. Should my theory prove untrue, France will say that I am a > // German and Germany will declare that I am a Jew." > // -- Albert Einstein > >
