aboutsummaryrefslogtreecommitdiff
path: root/src/os/unix/ngx_linux_init.c
diff options
context:
space:
mode:
authorMaxim Dounin <mdounin@mdounin.ru>2011-12-26 11:15:23 +0000
committerMaxim Dounin <mdounin@mdounin.ru>2011-12-26 11:15:23 +0000
commit822fe46934435956b710c781aa0dde7e5044e929 (patch)
tree23d6bea9fd32e4d63480487fc9fd12823d7bf343 /src/os/unix/ngx_linux_init.c
parent0c88994a0370af04ed1d9dc09f16e695bfd0a343 (diff)
downloadnginx-822fe46934435956b710c781aa0dde7e5044e929.tar.gz
nginx-822fe46934435956b710c781aa0dde7e5044e929.zip
Cache locks initial implementation.
New directives: proxy_cache_lock on/off, proxy_cache_lock_timeout. With proxy_cache_lock set to on, only one request will be allowed to go to upstream for a particular cache item. Others will wait for a response to appear in cache (or cache lock released) up to proxy_cache_lock_timeout. Waiting requests will recheck if they have cached response ready (or are allowed to run) every 500ms. Note: we intentionally don't intercept NGX_DECLINED possibly returned by ngx_http_file_cache_read(). This needs more work (possibly safe, but needs further investigation). Anyway, it's exceptional situation. Note: probably there should be a way to disable caching of responses if there is already one request fetching resource to cache (without waiting at all). Two possible ways include another cache lock option ("no_cache") or using proxy_no_cache with some supplied variable. Note: probably there should be a way to lock updating requests as well. For now "proxy_cache_use_stale updating" is available.
Diffstat (limited to 'src/os/unix/ngx_linux_init.c')
0 files changed, 0 insertions, 0 deletions