5,085 karma · joined March 11, 2009
* If this becomes popular it has the potential to skew logs and stats. Consider what happens when a bunch of prefetch requests are made to one of your pages, but the user never actually visits the page. The server (or stats package) doesn’t know the difference.
To clear this up, Firefox sends along an HTTP header, X-moz: prefetch, but you need some logic on the server side to detect it.
Multiply that by say, 130,000 people, and you are dealing with 325 people who don't receive their download, etc. and are not happy!
I think what would be really awesome is a regex that catches these common typos and warns the user immediately.
If you are correct, there is a massive conspiracy at Google, where a single whistleblower would be able to cost the company billions of dollars.
I have to admit I am having some trouble installing this and setting up a sample project.
Chrome can be with a runtime flag.
FireFox has an about:config flag.
http://i.imgur.com/amWMy.png vs. http://i.imgur.com/ysH0a.png
(As an aside, note that FireBug doesn't know that the font color has been overridden by the font tag.)
I'm curious what changes specifically you would make to improve it?
P.S. have you considered AppScale to migrate off of Google's infrastructure? Google has been funding a project that is a complete clone of the App Engine API, but can run on arbitrary hardware using MongoDB or a plethora of other middleware.
I think we've hit the max comment depth, and I think it's time to turn on the noprocast settings again. ;)
Are you accusing Google of falsifying this trivially reproducible and abundant data? That would be quite an interesting story. ;)
[1] http://code.google.com/status/appengine/detail/memcache/2010...
[2] http://code.google.com/status/appengine/detail/datastore/201...
[3] http://code.google.com/status/appengine/detail/datastore/201...
Secondly, 3 millisecond memcached access is several orders of magnitude too slow? 3 nanosecond memcache access would be quite a physical achievement. ;)
Reduced error rate with Automatic Datastore Retries - We've heard a lot of feedback that you don't want to deal with the Datastore's sporadic errors. In response, App Engine now automatically retries all datastore calls (with the exception of transaction commits) when your applications encounters a datastore error caused by being unable to reach Bigtable. Datastore retries automatically builds in what many of you have been doing in your code already, and our tests have shown it drastically reduces the number of errors your application experiences (by up to 3-4x error reduction for puts, 10-30x for gets).
Update: You guys scared me, so I just called Apple directly. They said that the official policy is that you have 14 days to exchange an opened Apple product, but in the case of the iPad it is common for Apple Store employees to extend this to 30 days (I now see the 30 day extension note on my receipt).
I did not get the phone call in writing though, but as I mentioned, you can verify it for yourself. ;)
I don't have the specific documentation that says this is the case, but I personally canceled my 3G iPad preorder and bought a WiFi model yesterday at the advice of an Apple Store employee.
Just call your local Apple Store and they will verify it for you.
Go ahead and call your local Apple store if you don't believe me. :)