On Feb 6, 12:50 am, "Florent Aide" <[EMAIL PROTECTED]> wrote: > The problem is I am not an rfc2616 expert but there seem to be much > more options and I don't have a clear idea of how to give access to > all this easily. > > The easiest route seems to just give a cache_control parameter and > then let the user specify this header by himself (not really friendly > but powerful) and the second route is to provided different arguments > that help people set an header without having to fully read and > understand the rfc2616...
First, I find overloading "expose" in this way pretty ugly. Sorry. :/ There has to be a limit on what a single function can do, and this goes *far* over that line (mostly because that line was crossed long ago anyway, IMO). Second, why not take 5 minutes and port cherrypy.lib.caching.expires from CP 3? Then you'd not only have a nice tool, but a forward- compatible one to boot. Robert Brewer System Architect Amor Ministries [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
