Opened 14 years ago
Closed 12 years ago
#16785 closed New feature (fixed)
Document cache design in `misc/design-philosophies`
| Reported by: | jamesp | Owned by: | Tim Graham |
|---|---|---|---|
| Component: | Documentation | Version: | 1.3 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
I initially found the design of the cache backend classes confusing, especially with respect to references to Memcached in django.core.cache.backends.base.BaseCache.validate_key() . I found that this was added a year ago in ticket #6447, so I figured there was a good reason but it was not explained anywhere I could find.
I discussed this with a couple core developers and hopefully the attached patch will be suitable.
Attachments (1)
Change History (4)
by , 14 years ago
| Attachment: | docs-misc-design-philosophies-cache.patch added |
|---|
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Patch needs improvement: | set |
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Uncategorized → New feature |
comment:2 by , 12 years ago
| Owner: | changed from to |
|---|
Since we can't get clarification on the "explicit vs. implicit" section, I'm going to commit the rest of this.
comment:3 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Not having been privy to the discussion on the issue, I'm a little unclear on what problem the last section on Explicit vs. Implicit is trying to address. While I agree with the sentiment I'm left with the question "why would it be tempting to do the opposite?"
Otherwise the patch looks good. If you could say a few words on the meaning of that last section I'll wrap it up and commit it.