The Cache Framework - Poco

More documents

Recommendations

Info

Overview > Motivation > Features > Interface > Examples > Performance Costs > Memory Costs
Why Caching? > STL containers make a good job in allowing you to store data > but you can't limit the size of the container, a map/set can potentially grow to infinite size > you can't let elements expire > POCO's caching framework supports exactly that > only std::map like behavior is supported so far > don't use caching if you don't need these properties (more on that in the "Costs" section)
Page 1: The Cache Framework Keeping things
Page 5 and 6: Classes > Poco::LRUCache #include "
Page 7 and 8: Interface: AbstractCache > Realized
Page 9 and 10: Interface - Events > FIFOEvent Add
Page 11 and 12: Time Based Expiration > ExpireCache
Page 13 and 14: Expiration based on last access tim
Page 15 and 16: Cache Performance > A cache is slow
Page 17 and 18: Cache Performance (Memory) > Abstra
Page 19 and 20: Cache Performance (Memory per Entry
Page 21 and 22: Tips (cont'd) > don't use has() fol

The Cache Framework - Poco

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?