git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5165 d4fa192b-c00b-0410-8231-f00ffab90ce4

and just leads to confusion.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5163 d4fa192b-c00b-0410-8231-f00ffab90ce4

log tags for a connection, and clear the collected log data on seeing the open
tag. This resolves an issue with log data where varnishncsa would consider a
set of data as bogus because of extra data in the log belonging to the previous
connection.

Support case 164.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5162 d4fa192b-c00b-0410-8231-f00ffab90ce4

Add explicit log flushing when backend connections close to keep log chronology. This is to avoid log lines for the same (reused) FD coming before the closing connection when load is high.

Fixes #739


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5160 d4fa192b-c00b-0410-8231-f00ffab90ce4

actually need it.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5158 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5157 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5156 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5155 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5154 d4fa192b-c00b-0410-8231-f00ffab90ce4

clashing with include/vmod.h



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5153 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5152 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5151 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5149 d4fa192b-c00b-0410-8231-f00ffab90ce4

Add code to implement function calls, based on symbols.

Add type-single-char values to definitions in vcc_types.h.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5148 d4fa192b-c00b-0410-8231-f00ffab90ce4

Emit a VCC friendly specification string for each functions.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5147 d4fa192b-c00b-0410-8231-f00ffab90ce4

Add the VRT functions for importing a module.

Tie the vmod_std module into the build.

The initial VCC bits for modules snug into the previous commit.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5146 d4fa192b-c00b-0410-8231-f00ffab90ce4

the standard functions supported in VCC.

For now put the very magic python script that ties the C code to the
VCL typesystem and the VCC compiler here.  Eventually it goes elsewere.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5145 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5144 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5143 d4fa192b-c00b-0410-8231-f00ffab90ce4

Keep track of constant subexpressions and use it avoid building
multipart constant strings on the workspace, when the C-compiler
will happily build them for us at compile time.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5142 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5141 d4fa192b-c00b-0410-8231-f00ffab90ce4

Use it for Expressions



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5140 d4fa192b-c00b-0410-8231-f00ffab90ce4

that cause them, rather than try to patch all the indentation
warnings they cause wherever they are used.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5139 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5138 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5137 d4fa192b-c00b-0410-8231-f00ffab90ce4

Remove some debugging that snug into last commit



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5136 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5135 d4fa192b-c00b-0410-8231-f00ffab90ce4

the thrad workspace.

Fix multiplication.

Cleanup indentation in C-source output




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5134 d4fa192b-c00b-0410-8231-f00ffab90ce4

Get precedence of the implicit cast to STRING right.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5133 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5132 d4fa192b-c00b-0410-8231-f00ffab90ce4

For now we assemble the string in the worker threads workspace.

I will reintroduce the optimization to pass it to VRT uncollected
where appropriate, once I get the new expression system pushed through.

Add a hacked up "regsub" function call for now, once functions gets
introduced it should be treated like any other function.

Add "true", "false" BOOL constants, REAL constants

Move the "set" statement over to the new expressions.

Fix testcases to use new string concat syntax where applicable.

"set req.url = 1;" was impossible before, now it works.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5131 d4fa192b-c00b-0410-8231-f00ffab90ce4

the way we learned to do it back in the 1950'ies.

Until now, VCC has used sort of a massaged C-expression and with
the introduction of things like regexp matching and ACLs that turned
sort of ugly.

This code is classic recursive expression parsing with a couple of
twists:

1. We don't build a tree, because we are not going to optimize stuff,
   we leave that to the C compiler.

2. Instead of the tree we build a string with magic markers that
   let us get the indentation of the produced C code right anyway.

3. We do type-hinted parsing, in an attempt to produce intelligent
   error messages and sensible semantics.

This code passes all testcases with a single change:  We can now
compile "if (2 == 3)".  This is probably a good thing (?)

Beware of bugs...




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5130 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5129 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5128 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5127 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5126 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5125 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5124 d4fa192b-c00b-0410-8231-f00ffab90ce4

two (IPv4/6) available sockets.  In this case, writing the :0 into
the VSM will not tell varnishadm where to look.

Write the actual socket addresses, one per line instead, and have
varnishadm try them all.

Make -n mutually exclusive with -S and -T on varnishadm.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5123 d4fa192b-c00b-0410-8231-f00ffab90ce4

as a socketaddr.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5122 d4fa192b-c00b-0410-8231-f00ffab90ce4