yeah, maybe this is a wicket-stuff project for now (if at all).
Eelco Hillenius wrote: > > On 4/14/07, Jonathan Locke <[EMAIL PROTECTED]> wrote: >> >> >> why wouldn't you want to cache a panel? you'd get all the normal >> nice wicket components and markup, but it would only render once >> in a while to a shared buffer. i don't think this is really involved in >> IResourceStreams. that seems like a separate issue. i just think it >> would be extremely convenient to be able to say "i've got this lame >> database query i don't have time to optimize or i want to retrieve >> (as you said) some remote resource and i want that cached and >> displayed in a panel that's updated every 3 minutes". i think that's >> a very transparent (no new API except for the method override) and >> very powerful way to get something done quickly. with panel caching, >> you can turn a non-performant database query into something that >> scales for a large number of users in a few seconds. without it, you've >> got a lot of work to do in the DB layer that requires quite a lot of >> specialized knowledge. > > But again, it's really the models behind the components you should be > tweaking. I'm afraid that making caching output a core capability of > components will distract users to much of what they're really should > be looking at (models). Also, if you really want, you can make such > caching components yourself today, which let's me doubt even more we > need to provide this as standard functionality. > > Eelco > > -- View this message in context: http://www.nabble.com/Serving-Static-Pages-with-Wicket-tf3572749.html#a9997442 Sent from the Wicket - Dev mailing list archive at Nabble.com.
