> > The edge cache is just that - a cache. It doesn't guarantee that no 304
> > requests will reach your app, only that they will be satisfied by the cache
> > if possible - and if the headers you set permit it. The more popular your
> > content is, the more effect you're likely to see from the cac
> > The onus is always on you to have as many levels of cache in place as
> > you can get away with so, depending on what you are caching, you are
> > going to benefit from using the edge cache, memcache, and instance
> > global variable caching all at the same time.
>
> Sure, but when designing ou
On Fri, Sep 16, 2011 at 11:22 AM, Bryce Cutt wrote:
>
> The onus is always on you to have as many levels of cache in place as
> you can get away with so, depending on what you are caching, you are
> going to benefit from using the edge cache, memcache, and instance
> global variable caching all at
Original Message-
From: google-appengine@googlegroups.com [mailto:google-appengine@
groups.com] On Behalf Of Jeff Schnitzer
Sent: Friday, September 16, 2011 11:29 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: Status of edge cache?
On Fri, Sep 16, 2011 at 11:22 A
I'd also like to see a rough idea of what to expect from the
edge-cache layer included in the documentation.
On Fri, Sep 16, 2011 at 13:29, Jeff Schnitzer wrote:
> On Fri, Sep 16, 2011 at 11:22 AM, Bryce Cutt wrote:
>>
>> The onus is always on you to have as many levels of cache in place a
On Fri, Sep 16, 2011 at 2:22 PM, Bryce Cutt wrote:
> I think Nick meant that popular content is less likely to be evicted from
> the cache, not that it is only cached if it is popular.
>
Oh, thanks, Bryce.
On Sun, Sep 18, 2011 at 1:49 AM, Robert Kluin wrote:
> I'd also like to see a rough ide
