I can't imagine a more sensible write-up of the issue.
I'm hoping Google responds. Yes, the forums are full of idiots
who really need to RTFM, but seeing important and sensible issues
like these go unanswered week after week really gives me the willies
about running my serious app on Google's
Just noticed this. This disables the IE8 XSS security filter.
Many Google sites seem to be sending it. It's odd.
Regardless, on AppEngine, seems like it should be left to the app to
decide and not Google.
I'm seeing it on static pages so I don't think it's Django or webapp.
Anyone know what's
In 1.2.4 Google added per-request detailed cost and cpu timing
information in the headers.
See http://googleappengine.blogspot.com/2009/08/new-features-in-124.html
I've submitted a patch to Firebug that cleanly integrates these
details into the Net panel.
It shows individual amounts per request
! :)
Here's a screenshot:
http://cloud.github.com/downloads/chadwackerman/FireEngine/screenshot.gif
If someone out there can help package it up, here's the project:
http://github.com/chadwackerman/FireEngine
I'm open to all help, moving to Google Code, whatever. Thanks!
On Sep 30, 6:27 am, Nick
I want to verify programmatically that thing and stuff belong to
the same entity group.
Anyone know the mojo?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send
Hit the same issue while developing my app.
Perfecting the development environment is the ideal goal here,
but a list of reserved names would be helpful.
On Feb 27, 11:05 am, johntray john.tur...@gmail.com wrote:
I have this unusual problem where the online server cannot find a
python module
Definitely #2
#1 also creates additional data integrity issues since, worst case,
29.9 seconds may elapse between the first and second call to get()
Depending on what you're doing with the data, you may need to put #2
in a transaction in order to get the results you expect
While I realize that this does not apply to the production
environment, I am doing some unit testing locally where I need the
datastore in a known state.
Since 1.1.9 I'm seeing more cases where put() followed immediately by
get() doesn't return the updated object -- probably due to improved
