[google-appengine] Re: Design consideration

2009-02-01 Thread gops
if you really need to get the list of places from just distance point of view -- you might consider to upload your data to google base -- add location to your items and use their query engine for your specific needs. it will be lot faster. and almost no performance issue. On Jan 29, 11:15 pm,

[google-appengine] Re: Design consideration

2009-01-31 Thread djidjadji
The strength of GAE is to handle many simultaneous requests (scalability). If they only read objects then there is absolutely no lock problem. If multiple requests want to write-to/update a single object/entity-group you can get collisions. They are resolved by executing your code in a

[google-appengine] Re: Design consideration

2009-01-29 Thread arnie
Using a distance range with subsequent filter to return only 25 rows is a good idea. Even if I pass a distance range in request url say from=0.1 and to=0.9 still then one needs to write this SELECT * FROM myTable as I cannot use limit statement here If multiple iphone users are accessing the wsgi