the `view_config` issue I encountered is that there is essentially no native way to return HTML. view_config supports most other types (templating engines, json, plaintext) but not HTML. that's very awkward to me.
-- a lot frameworks have application-level page/view/response caches. the more simple implementations cache the html or html+headers, the more robust ones selectively cache header elements. Pylons has a `@beaker_cache` decorator for controller actions (views). http://pylons-webframework.readthedocs.org/en/latest/caching.html Django has a `@cache_page` for views https://docs.djangoproject.com/en/1.7/topics/cache/ Turbogears has a `@cached` http://turbogears.readthedocs.org/en/latest/turbogears/caching.html Cherrypy does the page caching at an application level in the config files. i don't think you can enable/disble for views, just the entire app. Flask supports a Caching Decorator "pattern" that works on views. http://flask.pocoo.org/docs/0.10/patterns/viewdecorators/#caching-decorator -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
