-Using Dogpile for Caching
+Using dogpile.core for Caching
Dogpile is part of an effort to "break up" the Beaker
+ogpile is part of an effort to "break up" the Beaker
package into smaller, simpler components (which also work better). Here, we
illustrate how to approximate Beaker's "cache decoration"
function, to decorate any function and store the value in
-The Dogpile lock will ensure that only one thread at a time performs ``slow_database.lookup()``,
+The Dogpile lock will ensure that only one thread at a time performs ``slow_database.lookup()``,
and only every 3600 seconds, unless Memcached has removed the value in which case it will
be called again as needed.
Dogpile's system allows us to call the memcached get() function at most
+In particular, ogpile's system allows us to call the memcached get() function at most
once per access, instead of Beaker's system which calls it twice, and doesn't make us call
get() when we just created the value.
-Scaling Dogpile against Many Keys
+Scaling dogpile.core against Many Keys
The patterns so far have illustrated how to use a single, persistently held
:class:`.Dogpile` object which maintains a thread-based lock for the lifespan