#14399 closed Uncategorized (invalid)
Site's get_current() not thread safe?
| Reported by: | German M. Bravo | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.2 |
| Severity: | Normal | Keywords: | |
| Cc: | German M. Bravo | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Is the Site caching system thread safe? I don't think it is. The patch in Ticket #7517 (as well as the code for get_current()) will get invalid or deleted sites when Site objects get deleted/updated in other thread other than the one using get_current(), since the objects wont get invalidated from such other threads to the one making the request.
I would believe shared memory is needed for that, to invalidate the object in all threads (it can be done using a "sync" time in a shared memory medium (memcache even))
Change History (2)
comment:1 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 12 years ago
| Cc: | added |
|---|---|
| Easy pickings: | unset |
| Severity: | → Normal |
| Type: | → Uncategorized |
| UI/UX: | unset |
Note:
See TracTickets
for help on using tickets.
No, it appears to me to be fine. If something you get out of the cache gets invalidated during the course of your request there's nothing sane we can do about this, *all* caching solutions will suffer from this problem.