> > I was reading the Django definitive guide and practicing on 0.96.2 > > *but* caching is seriously broken on that version. I mean seriously. > > Almost all of my issues were gone with a simple upgrade. I switched > > from the book to the docs but still have questions. I would really > > appreciate any help at all here! > > I suggest upgrading to 1.0 or even the trunk version. I've been using > trunk and updating regularly, it is very stable.
I am sorry. I mentioned upgrading but that could have easily been mistaken for 0.96.3. Sorry again, I did upgrade to 1.0. Caching on 0.96.2 was terrible. Very very broken and 1.0 cleared up so many headaches. > > 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 :( > You have not mentioned how you are deploying your django project > (apache, development server?) nor what cache backend you are > attempting to use. I am currently studying Django and have used all backends available during testing on the development server. All backends work and I never came across an instance where using any one of them resulted in failure. As far as I know and am concerned, caching does work in Django. My main issues are small. query arguments, Cache-Control directives and a little more insight on *CacheMiddleware. > > Q. Are Cache-Control HTTP directives meant for public, browser and > > upstream caches beyond my control? I have finer grain tools for some > > of this stuff don't I? > Can't answer that one. >From what I took away on reading the book and docs was caching of my pages exist beyond my control *but* I can still be in control of what is cached. The thing is, I don't know how to actually see this and I don't know if it actually works. If I have to blindly trust that everything is done right I feel this may be a matter of quite some importance. I guess my real question here, is, is there any way to actually test and make sure these directives are being honored? > > Q. UpdateCacheMiddleware and FetchFromCacheMiddleware are how things > > should be done now *but* CacheMiddleware still works. I'll take your > > word on getting rid of CacheMiddleware in favor of the former > > middleware *but* does CacheMiddleware still play a role I should at > > least be aware of? > CacheMiddleware is the older middleware used to support caching. > UpdateCacheMiddleware and FetchFromCacheMiddleware are newer, and are > now the preferred way to do things. 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. Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
