repeat the GQL operation then reset all memcache items again in
the memcache set.
is this the only way?
On Oct 28, 6:07 pm, Nick Johnson (Google) nick.john...@google.com
wrote:
Hi loell,
Memcache is, as the name implies, a cache. Any key may be evicted at any
time, though frequently read
Hi i would just like to ask a related question with memcaching data
from the datastore, so what's the effective design with datastore
memcaching? is it just?
evaluate all items in the memcache set, and if there is no none
then
OK.
else repeat the GQL operation then reset all memcache items
hi, being used to the development's server, handling of memcache, and
that memcache items stays as long as it can. I'm really puzzled why
some of my items returns None while part of that particular memcache-
set is still retrievable on the production server. is this normal?
additional info: the Items in question are still retrievable in just a
couple of minutes, usually. but after that, it just returns none.
while part of the items in that set is still retrievable and all other
memcache sets are still intact.
On Oct 28, 1:48 am, loell loellanth...@gmail.com wrote
), with the least recently used
items evicted first.
On Oct 27, 1:56 pm, loell loellanth...@gmail.com wrote:
additional info: the Items in question are still retrievable in just a
couple of minutes, usually. but after that, it just returns none.
while part of the items in that set is still
$.post(/gettags,{ppa_name: '{{ppaname}}' }, function
(data ,textStatus){element.innerHTML = data; } )
I'm puzzled why this piece code is properly working on localhost, but
when deployment it won't.
does jquery's post method works for you? or are there any caveats
that i should know?
