Backlog #1107

Improve robustness in pool cache

Added by Carlos Martín over 9 years ago. Updated over 3 years ago.

Status:ClosedStart date:02/03/2012
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-

Description

Cached pool objects are indexed twice, by ID and Key (name-owner).
The pool object lock mechanism is closely related to the pool mutex and cache, but it can be managed by any other component.

We should simplify the cache to make it easier to add new features in the future.

History

#1 Updated by Ruben S. Montero over 9 years ago

  • Target version deleted (Release 3.4)

#2 Updated by Ruben S. Montero about 8 years ago

  • Priority changed from Normal to Low

#3 Updated by Ruben S. Montero about 8 years ago

  • Tracker changed from Feature to Backlog

#4 Updated by Ruben S. Montero about 8 years ago

  • Status changed from New to Pending

#5 Updated by Ruben S. Montero over 3 years ago

  • Status changed from Pending to Closed

Also available in: Atom PDF