hi,
we have exaclty the same problem. our application uses the page speed
service and since november 27.th we had this problem once, today (november
30.th) again.
i had to flush the pagespeed service to repair.
what can be done? our application is offline if the pagespeed service does
deliver
Had similar problems, too. Very high response time for all request and
datastore writes failed. The dashboard shows a lot of errors, but I
can't see any error in the logs. Now it is working again.
When I signed up for App Engine, I thought it would be rock-solid,
because it is powered by Google. Mo
On 05/07/2010 02:43 AM, Stephen wrote:
On May 6, 9:40 pm, Ulrich wrote:
Hi,
I am seeing a lot of "204"-responses in my logs. What does this mean?
Could be this:
http://www.kyle-jensen.com/proxy-caching-on-google-appengine
Thanks. After looking at the logs aga
Hi,
I am seeing a lot of "204"-responses in my logs. What does this mean?
Wikipedia says: "204 is the HTTP status code indicating the request was
received but there is no response to the request", but this information
does not really help me to understand why this is h
gh! If you
decide later that you want the property indexed after all, changing it
back to |indexed=True| will only affect writes from that point onward.
Entities that were originally written with |indexed=False| will not be
re-indexed."
You will have to re-put every entity that is not indexed
not indexed (indexed=False)
at the time you were adding these entities?
-Ulrich
Other fields in these records work as expected.
Anyone had similar problems/know what could be happening?
-Grant
--
You received this message because you are subscribed to the Google Groups "Google
self.data_version entity inside the transaction or
outside of it?
-Ulrich
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this gr
not have to generate them
in the background with a task.
-Ulrich
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email
nickmilon wrote:
Acording to Nick Johnson : " The simultaneous dynamic request limit
was eliminated in a recent SDK "
But afaik the average response time should be < 1 second.
-Ulrich
On Apr 16, 9:22 am, Nickolas Daskalou wrote:
If you're keeping your AJAX conne
ests that are just waiting (and
doing nothing else)?
-Ulrich
-Nick Johnson
On Sat, Apr 10, 2010 at 2:12 PM, peterk <mailto:peter.ke...@gmail.com>> wrote:
I've been using and watching appengine since, well, the beginning, and
only by a random Google about an unrelated
daily
limits and maximum rates does not contain any information about https
requests. Does that mean that there is no limit other than the limit for
http requests?
-Ulrich
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" group.
To p
like long polling is not possible, too. But you could possibly
use the XMPP service
(<http://code.google.com/appengine/articles/using_xmpp.html>) for push
notifications.
-Ulrich
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" g
or a display a 404 error or something
like that.
-Ulrich
I could understand this being a
restriction on free accounts, but does it also apply to paying
customers?
Thanks!
Eze
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" group.
Or is it better to use something like:
random = random.SystemRandom()
because it does not use the Mersenne Twister?
-Ulrich
Ulrich wrote:
Hi,
I have a short question on a security aspect. To generate something
like a session ID or other random strings that need to be secure and
ous values
of topsecret that were generated by the same instance?
-Ulrich
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, s
n requests per day, you can talk to
us and we'll extend it. If you reach that without needing to pay for
any extra CPU quota, I'll happily buy you a beer and write a case
study about your app. ;)
A question: Is CPU used for static requests (images, html sites, etc.)? ;-)
-Ulrich
-
arch = u'abc'
I can think of two ways to do this:
>= search AND < search + u'\U0010'
which will not work if one of your matches begins with
search+u'\U0010'
but that is very unlikely...
And the other solution is
>= search AND < search[:-1] + unichr(
ike GEO IP does but from my system running on app engine.
Something like http://www.maxmind.com/app/ip-location could help you. I
would download the database and load it into the datastore.
-Ulrich
--
You received this message because you are subscribed to the Google Groups "Google
App En
solution was significantly faster than getting all keys with a
batch get.
SELECT * FROM Model WHERE __key__ >= :key_first ORDER BY __key__
(and fetching length(list) entities)
I don't know if your list of keys has a similar structure, but I thought
it could help you.
-Ulrich
Josh Rehm
often and
it will not work without some kind of sharding.
-Ulrich
On Mar 15, 10:12 am, Takashi Matsuo wrote:
Hi,
Perhaps you can order by salary property descending, and just get the
first one, for getting max value.
max_salaried_employee = Employee.all().order("-salary").get()
Hi,
I would recommend to base64-encode the binary data before url-encoding
it, because this method requires less space / bandwidth. In my opinion,
this is also easier to work with, especially if you use different
languages (AJAX etc.).
-Ulrich
Iap wrote:
Hi,
I have a weird problem: If I
Hi Nick,
Thanks for your fast answer!
Nick Johnson (Google) wrote:
Hi Ulrich,
On Wed, Feb 17, 2010 at 5:30 PM, Ulrich <mailto:mierendo...@googlemail.com>> wrote:
Hi,
I have read the following
"Timeouts due to datastore issues --- [...] The most common example of
Hi,
I have read the following
"Timeouts due to datastore issues --- [...] The most common example of
this occurs when you are rapidly inserting a large number of entities
of the same kind, with auto-generated IDs. In this case, most inserts
hit the same range of the same tablet, and the single tab
23 matches
Mail list logo
