Asset externalization always had some problems for handling a cluster. The new approach eliminates that problem in a couple of ways, mostly by sending a proper HTTP response code, allowing the client to cache the downloaded asset effectively.
On 11/23/05, Chris Burnley <[EMAIL PROTECTED]> wrote: > Oh, I see that asset externalization has was removed in beta-5. Why ? what > if I am storing images in a database and wan't them cached on disk > > On 11/23/05, Chris Burnley <[EMAIL PROTECTED]> wrote: > > > > I read somewhere in the Tapestry In Action book that it is possible to get > > Tapestry to cache assets on disk somewhere so that apache will pick it up > > instead of serving it from the webcontext. > > > > Does anybody know how to configure this feature ? > > > > regards, > > > > Chris Burnley > > > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
