A few days ago I posted some thoughts on how the response times for
some GAE applications might be reduced. Part of the idea was to track
hashes of the contents of files. It turns out there is a name for
this general approach--content-based addressing. Following is an
article that gives a good
Is the subdirectory that contains dev_appserver on your PATH? It
needs to be in order for the command shell to find it. On my own
laptop the subdirectory is /usr/local/bin, since I installed GAE using
the Mac OS installer. In .bashrc I have:
export PATH=snip:/usr/local/bin:snip
With your
Thanks for the suggestion. I'll try #3 as an first approach and see
where that takes me (and look forward to #5). I think app-engine-
patch has a main() declared, and I assume the app is getting cached as
a result, but I'm not sure if that's the case.
Re the file caching idea, I don't
Hi Arny,
The reason the offset works this way is related to bigtable and the
way the datastore has been implemented on top of it. If what you need
is paging, e.g., scrolling through a dataset of search results, there
are more efficient ways of doing this than using the offset. Some of
them are
Hi everyone,
I have a beginner's question I wasn't able to find documentation on.
I'd be grateful if someone could point me to a specific page or issue
number that discusses it.
I just finished debugging a simple pager that pages over a PolyModel
subclass using the __key__ in descending order.
