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

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

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

Remove #include bogohandling in vcl_gen_fixed_token.tcl



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

isolate the compiled code from the internal structures of the cache
process through of VRT functions.



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

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

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

Generate VGC prefixes instead of VCL.



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

Start putting some structure in the sources relating to VCL handling:

Split the runtime support for compiled varnish programs out and give it the
prefix "VRT".

Start using the prefix "VGC" for generated code.

Prefix "VCC" will be for the compiler and "VCL" for calling the compiled and
loaded functions.



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

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

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

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

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

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

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

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

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

can be centralized.

Remove old handling callbacks.

Call hit/miss methods instead of lookup method.


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

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

Make handling a named enum, and use it as a bitmap.

Add "lookup" reserved word

Add VCL_done() macro to use in compiled code to set handling and drop
the per-handling callbacks (apart from VCL_error())




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

Split vcl_lookup() in vcl_hit() and vcl_miss()



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

Improve chunked encoding, allocate big storage chunks and trim the
last one at the end, instead of one storage chunk for each chunk
the remote server sends.

Call RFC2616 policy code.

Store headers from backend in cache and return to client.



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

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

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

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

stored efficiently.


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

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

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

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

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

object from the sessions to the client.


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

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

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

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

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

Let storage_file use sendfile(2) for it.



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

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

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

constraint in FreeBSD and we shouldn't really listen to it.

On my laptop I can mmap 2422MB file this way.

This may be so aggressive that it leaves insufficient address space for
malloc/threadstacks and other issues.

If we find a way to pick up a platform/architecture specific limit, we
can enforce that along the way.

For now people can just specify a saner and smaller "-sfile" size.



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

the stevedore.

This should probably be (fine-)tuned later on as it might be too aggressive
when faced with user errors.

Also, might it be possible to mmap() more than MAX_SIZE_T bytes if
it is done in multiple calls ?



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