From 4d0b5c8bf061c309a3472b4e2146e0a1f8166c78 Mon Sep 17 00:00:00 2001 From: des Date: Thu, 20 Jul 2006 11:15:16 +0000 Subject: [PATCH] Add missing end tags + whitespace cleanup git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@518 d4fa192b-c00b-0410-8231-f00ffab90ce4 --- varnish-doc/en/varnish-architecture/article.xml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/varnish-doc/en/varnish-architecture/article.xml b/varnish-doc/en/varnish-architecture/article.xml index 3e103b3e..2da2aa6d 100644 --- a/varnish-doc/en/varnish-architecture/article.xml +++ b/varnish-doc/en/varnish-architecture/article.xml @@ -1,4 +1,5 @@ + -
@@ -41,6 +41,7 @@ low complexity. The only major component apart from the CLI stream multiplexer is the VCL compiler. +
Cache Process Components @@ -50,7 +51,7 @@ have been constructed for maximum efficiency at the cost of some simplicity of structure. - +
Acceptor @@ -95,6 +96,7 @@ if the session is waiting for reasons where having the worker thread is not necessary for the waiting. + XXX: either list the major steps from cache_central.c here or have a major section on the flow after the components. @@ -170,6 +172,7 @@
Purge/Ban procssing + When a purge is requested via the CLI interface, the regular expression is added to the purge list, and all requests are @@ -177,15 +180,18 @@ The most recently checked purge is cached in the objects to avoid repeated checks against the same expression. +
VCL calls and VCL runtime + The state engine uses calls to VCL functions to determine - desired processing of each request. The compiled VCL code + desired processing of each request. The compiled VCL code is loaded as a dynamic object and executes at the speed of compiled code. + The VCL and VRT code is responsible for managing the VCL codes loaded and to provide the proper runtime environement -- 2.39.5