2008-6-6
| 01:21 | mua`dib | ahh....with the HTTP headers you can add you own fields right? |
| 01:27 | mattmcc | What fields are you referring to? |
| 01:27 | mua`dib | i was referring to the Cache-Control header |
| 01:28 | mua`dib | i mean field |
| 01:28 | mua`dib | trying to understand how the CacheMiddleware works |
| 01:29 | mattmcc | That'd be a reasonable topic for #django.. |
| 01:30 | mattmcc | But the cache middleware just sets that header based on the configured caching time. |
| 01:33 | mua`dib | so if i undersand this correctly Django sets the Cache-Control header field with a time and the browser does the timeout counting? |
| 01:35 | mattmcc | Well, the caching middleware does server-side caching. |
| 01:35 | mua`dib | yeah but how does it invalidate the cache after the default 300 seconds passes |
| 01:36 | mua`dib | does it invalidate all of the cache...or individual entries in the cache |
| 01:36 | mattmcc | It wouldn't be very useful if it invalidated the whole cache. |
| 20:44 | cramm | Hi guys, I'm trying to update an external database backend and in the process I thought it would be nice to abstract some django/db/models/fields/__init__ if setting.DATABASE_BACKEND == 'blah': to use some newly-created backend DatabaseFeatures fields |
| 20:45 | cramm | but it seems currntly no code at the fields level access the backend's DatabaseFeatures and this made me ask myself if my approach is really correct |
| 21:02 | cramm | hmm the guys working on the firebird backend are doing a similar thing |