]> err.no Git - varnish/commit
Give sessions a backend connection instead of a backend and
authorphk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Tue, 26 Aug 2008 09:17:32 +0000 (09:17 +0000)
committerphk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Tue, 26 Aug 2008 09:17:32 +0000 (09:17 +0000)
commita5f9cb12eebbb95677baf8a32a8aacd3e39bc89a
tree2748d3cfe07ad865826bd67f705dd8e4624fb45c
parentb042c041f18c15bf79ed0c1ebd777143ac33bb89
Give sessions a backend connection instead of a backend and
have the directors provide that.

Entirely a no-op, apart from a bugfix that just would screw
you even more (than "totally") if socket(2) should ever fail.

git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@3129 d4fa192b-c00b-0410-8231-f00ffab90ce4
varnish-cache/bin/varnishd/cache.h
varnish-cache/bin/varnishd/cache_backend.c
varnish-cache/bin/varnishd/cache_backend.h
varnish-cache/bin/varnishd/cache_center.c
varnish-cache/bin/varnishd/cache_dir_random.c
varnish-cache/bin/varnishd/cache_dir_round_robin.c
varnish-cache/bin/varnishd/cache_dir_simple.c
varnish-cache/bin/varnishd/cache_fetch.c
varnish-cache/bin/varnishd/cache_panic.c
varnish-cache/bin/varnishd/cache_pipe.c