Re: RFC: ETag support for zope.browserresource

On Tue, Aug 10, 2010 at 04:49:47PM -0300, Sidnei da Silva wrote:
> On Tue, Aug 10, 2010 at 12:42 PM, Marius Gedminas <[email protected]> wrote:
> > How would you like that to be configured?
> >
> > Option #1:
> >
> >  <browser:resource/resourceDirectory etags="off" /> ?
> >
> > Option #2:
> >
> >  getMultiAdapter((resource, request), IETag).computeETag() ?
> >
> >  This is maybe a bit problematic, because the actual File object that
> >  contains all the data--such as filename--doesn't implement any
> >  interfaces.  And neither does FileResource.
> 
> So maybe Option #1?

But then it's not easily overridable, globally, for a particular
application, since each package may have its own browser:resource
declarations.

Option #3:

  IResourceETag(request).computeETag(path, timestamp, data)

Feels a bit ad-hoc.

Option #4:

  let people who want ultimate cache control use something else than
  zope.browserresource for serving static files.

Feels a bit unfriendly (but Zope 3/Bluebream is usually pretty
unfriendly...)

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 )

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkxhvH0ACgkQkVdEXeem14/oGQCeMBfDM5wURy7qh7eseSAaqFdQ
FYoAn210l+m+lKfUiUrRuuq8HjRi366t
=JOUO
-----END PGP SIGNATURE-----