On Sep 12, 11:11 am, vbgunz <[EMAIL PROTECTED]> wrote: > > > > Q. At what point in time do the query arguments come into play for > > > CACHE_BACKEND? Is it only a certain combination of arguments? Does > > > CacheMiddleware, UpdateCacheMiddleware, FetchFromCacheMiddleware play > > > any part at all with these arguments? Do only certain caching > > > interfaces accept these arguments? Are these arguments for upstream > > > caches e.g., squid-cache.org, ISP? > > > Not real sure what you mean. The arguments control how things are > > cached, regardless of the backend or middleware. > > I virtually used every backend available and many combinations of > arguments and looking for a simple timeout of 15 seconds is > impossible. I tried db://. memcached://, file:///, and the rest and > although caching on a global scale always works and modifying them > with some of the caching decorators work as advertised, I never once > managed to get the query args to CACHE_BACKEND to work. > > I use Firefox and the Web Developer extension and check my response > headers by going to Information > View Response Headers. Although > every thing I've done on 1.0 in regards to caching shows up in that > informational window, I never seen query arguments to CACHE_BACKEND > show up in any way. I just did not take away anything positive from > the book on 0.96.2 OR the docs on 1.0 in this matter. I never see the > query arguments in action :(
But those arguments don't go out in headers, they are consumed internally to django to control how long it puts things in the cache. Also remember you have the source code to django. Look in it to see how those parameters are being used. > > I am aware of the newer *CacheMiddleware. I can do them without any > problem I just noticed that CacheMiddleware still works and didn't > notice a big change. I didn't really get too much about it in the > docs. This is no bigge compared to my other questions. > Try searching the tickets to see the history of the development and why they went to 2 new pieces of middleware. I don't know if you will find anything, but that is what I would do if I had your question. Remember that django, especially prior to 1.0, was evolving and stuff changed. If you feel something isn't documented properly, write a ticket. > Thanks HTH --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
