That decorator is really neat! Especially the part where it ignores
cache when debugging =) Thanks for the link!
And thanks for your input, I'll consider doing something like that and
then we'll just see how it goes once my application starts taking
visitors =)
- Andreas Blixt
On Jan 22, 9:58 pm
Maybe you can use both your approach+memcache. Look for stuff in the
local cache first. If not found, go to memcache, if not found, then
load from the datastore. This can be neatly hidden in a decorator.
See:
http://appengine-cookbook.appspot.com/recipe/decorator-to-getset-from-the-memcache-autom
Yup, I know, that's what brings forth my questions about the large-
scale behavior of in-memory caching. Will the instances be recreated
too often for it to be more effective than memcache? Will there be too
many instances at a time for it to be more effective?
I also rewrote the code to use prop
The big difference between in-memory caching and memcache caching is
that memcache data is shared between all of your running instances,
but in-memory caching is on a per-instance basis.
On Jan 22, 9:52 am, Blixt wrote:
> Hi there,
>
> I've been playing with caching using global variables
> (s
