Re: The state of per-site/per-view middleware caching in Django

On Thu, Oct 20, 2011 at 7:45 AM, Jim Dalton wrote: > There > is still an exceptionally narrow set of circumstances that would allow me to > serve a single cached page to all anonymous visitors to my site: namely, I > can't touch request.user and I can't use CSRF. This

Re: Multiple email connections

On Wed, Feb 23, 2011 at 11:44 AM, Luke Plant wrote: > Is it not possible to do this already, by writing your own backend that > splits up e-mails as you see fit? Yes, but it'd be nice if the get_connection arguments for each connection type could be easily referenced by

Multiple email connections

Multiple databases and caches can currently be configured in one's settings file. It'd be nice if the same could be done with email connections. For example, Amazon's SES starts out new users with a low quota that they gradually increase, so splitting emails between SES and other connections to

CACHE_MIDDLEWARE_ANONYMOUS_ONLY should be removed

In the documentation, CACHE_MIDDLEWARE_ANONYMOUS_ONLY is promoted as "a simple and effective way of disabling caching for any user-specific pages." This may have been the case if user-specific requests didn't use to have the Vary: Cookie header added on automatically or the cache middleware didn't