I actually think it was a temporary glitch, I have not seen it at all since when we first reported it.
I am in the same boat as Adam, I designed my page to make lots of simultaneous request (via an xmlhttprequest) instead of doing all the hard work in the main web page... Its a hard one, because if google tell us the thresholds for triggering this then it is open to abuse up unitl that limit. You can stop one person from abusing the site by blocking them from making requests over this threshold, how would you do it for 1000 machines from different networks hitting your site to just below the threshold regularly. To get to Jays argument. although I am not keen on it, as per my original email, I have had time over the weekend to think about it. I think we all need protection from malicious use, after all, everything on this service will be directly monetisable (above the free quota) and with the services that I run, I don't want to spend money on people who are not interested in my site. I would however like some control over what would be blocked, after all I will be exposing API's to clients when the GAE is out of "beta" and if it was a traditional unix host (for instance) I would have control over the ip addresses/ranges that have access to my site. The point I was making about unfairly using a shared system is that unlike a traditional host where you have own machine on the network, GAE is not like that, your app potentially sits alongside my application, and if for some reason your site is getting hit by bots, it could easily mean that my site is affected. Obviously, I don't know Google infrastructure and it could be vast array of machines already set up for the GAE so the likleihood of you affecting my site may be minimal. Anyway, i think this issue may have been a storm in a tea cup (unless anyone is still get this error). Paul. 2008/11/17 Adam <[EMAIL PROTECTED]> > > > > On Nov 17, 1:07 am, "Jay Freeman \(saurik\)" <[EMAIL PROTECTED]> > wrote: > > :( I don't even understand "the need for this". > > > If/when I get to the point of paying for quota overages, it would be > nice if there was built in protection from someone setting up a cron > process to essentially drain money from my bank account by creating > 'fake' traffic. > > I'd just like some clarity on how this test works, so I don't trigger > it with AJAX calls on my page. CPU warnings made me thing 20 quick > calls were better than 1 or 2 slow calls, but if that shuts down my > app for a user after 20 seconds of navigation on the map maybe it's > not. > > > A > > > --~--~---------~--~----~------------~-------~--~----~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
