On Wed, Jul 6, 2011 at 8:00 AM, Pol i...@pol-online.net wrote:
On Jul 1, 10:10 am, Ikai Lan (Google) ika...@google.com wrote:
It's possible for two operations to update townCache concurrently, but in
your case it looks like it doesn't really matter. If TownModel is somehow
updated between
On Jul 1, 10:10 am, Ikai Lan (Google) ika...@google.com wrote:
It's possible for two operations to update townCache concurrently, but in
your case it looks like it doesn't really matter. If TownModel is somehow
updated between reads, it's theoretically possible for you to have an older
On Tue, Jul 5, 2011 at 8:47 AM, Joshua Smith joshuaesm...@charter.netwrote:
Thanks for that clarification. I'm sure there's a reason for this
asymmetry (must declare globals to write them, but not to read them), but
it's really weird.
Since Python doesn't require variable declaration at
Thanks for that clarification. I'm sure there's a reason for this asymmetry
(must declare globals to write them, but not to read them), but it's really
weird.
On Jul 1, 2011, at 6:12 PM, Geoffrey Spear wrote:
On Jun 29, 1:40 pm, Joshua Smith joshuaesm...@charter.net wrote:
I have this
On Jun 29, 1:40 pm, Joshua Smith joshuaesm...@charter.net wrote:
I have this code in one of my apps:
townCache = {}
def getTown(id):
if not id in townCache:
townCache[id] = TownModel.get_by_id(id)
return townCache[id]
Is this thread safe? I think it is, because the worst that
We are not going to have to go into that much detail for our apps
thought are we.
Will we be able to take advantage of the multi-threading by simply
creating multiple request handlers. I imagined I would be changing a
few lines of code in my main function an that's about it.
On Jun 29, 9:43 pm,
I don't believe you'll need to do anything when we ship concurrent requests
for Python, as long as you're not using global mutable state anywhere. It's
unlikely your threads will ever need to talk to each other.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog:
