vcl changes from 1.x to 2.0 documented for Red Hat

git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@3153 d4fa192b-c00b-0410-8231-f00ffab90ce4

diff --git a/varnish-cache/redhat/README.redhat b/varnish-cache/redhat/README.redhat
index f9a24d7f448b1b1197bbdf4be5ee02f81b7b6872..f9e02cb4f7da01fa9b22bf3c889247ac01582ef5 100644 (file)
--- a/varnish-cache/redhat/README.redhat
+++ b/varnish-cache/redhat/README.redhat
@@ -5,6 +5,24 @@ build varnish with. This means GCC 3.4.6 on a standard RHEL4 system.
 
 Varnish should work fine with GCC 3.3 and above.
 
+Upgrading from 1.x to 2.0
+=========================
+There are a few changes in the vcl language from varnish-1.x to 2.0.
+Because of varnish' dynamic vcl loading feature, there is no way to
+guarantee that the vcl file in use actually exists on disk. Thus,
+there is no way to securely automate this process, and one must do the
+changes by hand.
+
+In vcl, the word "insert" has been replaced by "deliver". 
+
+In the vcl declaration of backends, where one earlier used "set
+backend", backend parts are now just prefixed with a dot, so the
+default localhost configuration will look like this:
+
+backend default {
+  .host = "127.0.0.1";
+  .port = "80";
+}
 
 Configuration of addresses and ports
 ====================================