If caching does not work in HR this is a real problem. Could it be by design ? Have others observed this ?
happy coding:-) Nick On Mar 19, 10:32 pm, "Brandon Wirtz" <[email protected]> wrote: > So they are all in one place, here are the things I know to be an Issue with > HR: > > 1. Caching doesn't work, and because of the way headers are forced to > be set all requests expire immediately so the user won't cache either. > > (Headers from a request) > > HTTP/1.1 405 Method Not Allowed > Content-Type: text/html; charset=utf-8 > Cache-Control: no-cache, must-revalidate > Expires: Fri, 01 Jan 1990 00:00:00 GMT > Set-Cookie: S=apphosting=5hoCHm4x9c3ZrrxQEN5Q4A; path=/ > Date: Sat, 19 Mar 2011 19:37:21 GMT > Pragma: no-cache > Server: Google Frontend > Content-Length: 0 > > This happens even if you programmatically set output to have some other > expiration, pragma, and/or cache-control. > > 2. Charts in the dash board only go back 24 hours. > > Vs. up to 30 days for Master Slave. > > 3. Data Store Viewer always errors if you try to edit entities. > > This works most of the time when I use MS. (not always but mostly) > > 4. This isn't so much an "issue" as an observation. I get a higher > error rate on HR at the same time I get higher rates on MS. Sometimes I get > errors on MS and won't get them on HR, but it seems anytime my error rate > goes up on HR it is up on MS as well. > > Most of these errors are "memcache.add failed" [ ok in my app that is the > only error I ever get, but that's cause my code is perfect it's the platform > that has issues :-) ] > > image001.png > 43KViewDownload > > image002.png > 32KViewDownload > > image003.png > 51KViewDownload -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. 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.
