Re: RFC: ETag support for zope.browserresource
Marius Gedminas <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <20100811160032.GA23162@platonas> |
On Tue, Aug 10, 2010 at 11:54:21PM +0300, Marius Gedminas wrote: > Option #3: > > IResourceETag(request).computeETag(path, timestamp, data) > > Feels a bit ad-hoc. The more I think about this, the more I think it's best to configure etag policy by providing an adapter on the request. I think I'll go with some variation on this theme. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkxiySAACgkQkVdEXeem14+ejACffOM7L2Ihl8p2qKw3Bq5+23HZ ncUAnirNVVgauqUoof9GTIW3lPwCiPJA =PG9i -----END PGP SIGNATURE-----