-
Nils Goroll authored
The shard director had the limitation to only support adding/removing backends of one instance before `.reconfigure()` on that instance had to be called, then the next instance could be changed. This limitation came from the time when it was still unclear that calling `VRT_priv_task()` on a per-object pointer was the accepted interface for per-instance privs (varnish historians' recommended read: https://github.com/varnishcache/varnish-cache/wiki/VIP1:-PRIV_*-visibility-and-lifetime-control ) It is about time to lift that limitation now. o/ Dridi
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
Makefile.am | ||
automake_boilerplate.am | ||
fall_back.c | ||
flint.lnt | ||
flint.sh | ||
hash.c | ||
misc.c | ||
random.c | ||
round_robin.c | ||
shard_cfg.c | ||
shard_cfg.h | ||
shard_dir.c | ||
shard_dir.h | ||
vdir.c | ||
vdir.h | ||
vmod_directors.vcc | ||
vmod_shard.c |