This is great; I was just thinking that the asset service should allow for client caching of private assets myself. Now I don't have to go crack an RFC :-)
On 4/13/05, Viktor Szathmary <[EMAIL PROTECTED]> wrote: > > Hi, > > I am submitting two small patches for the following issues: > > 1) enable HTTP caching for private assets > > Now that private asset URLs include a mandatory MD5 hash, I consider > it safe to allow the browser to cache these indefinitely. If the > content ever changes, a different link will be generated. This change > reduces server requests significantly where private assets are used > (ie. all component libraries) without having to resort to tricks to > externalize these resources. > > 2) change visibility of Form.getLink to protected (from private) > > This allows subclassing the Form component and overriding the service > that will handle the request, without resorting to major copypasting > or other hacks. This came up during development of the Tacos > PartialForm component (see related emails on tapestry-user). > > Since the patches are trivial in nature, no unit tests are submitted. > > I hope a 3.0.4 release can be put together soon that includes these - > please consider this. > > Regards, > Viktor > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- 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
