1st iteration of volta actually doing something. Process the request,
find the best matching rule, and rewrite the request.
Without the DB queries, volta was parsing over 750k requests a second.
Currently, it's down to 129.5 with 1161 rules in place. Yikes. I may
need to re-evaluate some design choices here.
Building volta===============Volta should build with minimal effort and without external dependencies, except forGNU make. (http://www.gnu.org/software/make/)Compiling---------Just type 'make'. Depending on your platform, GNU make may have beeninstalled as 'gmake' If you get any errors, try 'gmake' first.It should build without warnings.Installation------------Volta doesn't contain any installation targets. You can put the binarywherever makes sense on your system. Note that it should be in adirectory that is writable to Squid, unless you plan to store thedatabase separately. An example: mv volta /usr/local/bin mkdir -p /var/db/squid chown squid:squid /var/db/squid volta -f /var/db/squid/volta.dbI usually just drop it into the squid configuration directory and run itfrom there.For usage information, see the README.Development-----------Volta source can be cloned via Mercurial. The repo is found at: http://code.martini.nu/voltaYou can use the 'debug' make target to compile a (very noisy) binarythat contains gdb symbols and perftool hooks. Set the CPUPROFILEenvironment variable to "cpu.prof" to generate a profile.If you're hacking, you'll want these dependencies installed too. - ragel (http://www.complang.org/ragel/) - mercurial (http://mercurial.selenic.com/) - google-perftools (http://code.google.com/p/google-perftools/) - graphviz (http://www.graphviz.org/) - ctags (http://ctags.sourceforge.net/)