Graham Leggett wrote:
For the expiration case, there's a much easier solution than
shadowing the
incomplete response. Add a new state for cache entries:
being_updated.
When you get a request for a cached object that's past its expiration
date,
set the cache entry's state to
Brian Pane wrote:
Graham Leggett wrote:
For the expiration case, there's a much easier solution than
shadowing the
incomplete response. Add a new state for cache entries:
being_updated.
When you get a request for a cached object that's past its expiration
date,
set the cache entry's
This patch allows mod_cache to cache a response that isn't
all contained in the first brigade sent through cache_in_filter().
(This scenario happens, for example, with reverse-proxy requests,
CGIs, and various app server connectors.)
Can someone familiar with the caching code please scrutinize
This patch allows mod_cache to cache a response that isn't
all contained in the first brigade sent through cache_in_filter().
(This scenario happens, for example, with reverse-proxy requests,
CGIs, and various app server connectors.)
Can someone familiar with the caching code please
Bill Stoddard wrote:
Adding a callback/hooks sounds okay. An additional problem to consider is
when a frequently requested resource does not return an EOS in the firet
brigade and it turns out to be too large for the cache. We need a negative
cache (what else would you call it?) to prevent
Graham Leggett wrote:
Bill Stoddard wrote:
Adding a callback/hooks sounds okay. An additional problem to
consider is
when a frequently requested resource does not return an EOS in the firet
brigade and it turns out to be too large for the cache. We need a
negative
cache (what else
Brian Pane wrote:
In the shawowing case, we'd also need a way for all the requests
reading from the same incomplete cache entry to block if they reach
the end of the incomplete cached brigade without seeing EOS. I guess
we could do this by adding a condition variable to every incomplete
Graham Leggett wrote:
Brian Pane wrote:
In the shawowing case, we'd also need a way for all the requests
reading from the same incomplete cache entry to block if they reach
the end of the incomplete cached brigade without seeing EOS. I guess
we could do this by adding a condition variable
