You remember correctly :) But i think it was in one of the mailing lists. Someone had asked if in 4.0 the meta property that copies assets to a folder in the current context still works, and he got the response that you're describing.
>From Patrick Casey <[EMAIL PROTECTED]>: > > > I seem to recall reading something about this in one of Howard's > blog entries, but when I looked back I couldn't find anything so I thought > I'd ask about it here. > > > > Lets say we have a component that serves up some static content > (like, say 4 .gif files that go on button faces). > > > > Since the content is served by the servlet, and the 3.0.3 > tapestry apps doesn't seem to implement getLastModified(), then every time > anybody loads that component, all 4 gifs flow down to the client. Given that > the gifs in question never change, they theoretically *could* be cached by > the browser, but it doesn't appear that Tapestry 3.0.3 does the awkward leg > work to support it (and it would be awkward). > > > > Does 4.0 now implement getLastModified() when requests are made > to the asset or other static services? As I said above, I seem to recall > reading that Howard had made this enhancement for 4.0, but I can't remember > where I read it, or even if I hallucinated it. > > > > --- Pat > > -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
