2010/12/13 Hraban Luyat <[email protected]>: > Hi all, > > A comment I made myself in a reply to another thread just now, got me > thinking: could web.py not simply provide HTTP caching out of the box? > By letting it analyse the output headers (cache-control, expires, etc) > just as any caching proxy would, it can do a lot of work for us, and > this would come for free from the developer's point of view. You could > perhaps make it an option to disable it, were you to have some more > powerful caching infrastructure in place, but otherwise I would not > see the harm in some proper, HTTP compliant caching mechanisms. I > think the benefits would far outweigh the cons. > > Anybody got any objections or further ideas?
I don't think that should be part of web.py. You can use something like varnish for doing that or write a simple WSGI middleware for doing that. Anand -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
