cleanup.
initial add vs2012 sln
initial add projects for some of the libs
Make sure that the ban-lurker cleans the tail at least once every
10 loops.  Simplify the structure of the code some more.

Prodded by:	martin
Get rid of ban_url/ban.url

ban.url is confusing as it takes a regular expression rather than a
fixed string, so get rid of it in favour of people being explicit and
using ban req.url ~ /foo
s/obj.cookie/obj.http.set-cookie/
Stop referencing the module index, since no such thing exists

Fixes #1233
Revert "Stop referencing the module index, since no such thing exists"

This commit included som unfinished work, so revert it.

This reverts commit d4f456f0326d02a94aed5c0b8143e77f6d180dc9.
Stop referencing the module index, since no such thing exists

Fixes #1233
Make vcl.use slightly more chatty

Output that we've switched VCLs and which one we have switched to when
using vcl.use.

Fixes #1232
A couple of style nits
Remove a pseudo-bogus test for pthreads in the manager process.

The subsequent cleanup/separation of .h files makes this test
much less important, and it's not like it is a conclusive or
comprehensive test in the first place.

Fixes	#1230
Add a BAN_Shutdown() routine that is called before STV_Close(), and
makes sure that the ban lists will not change until we exit.

This is to give persistent stevedores a chance to clean up their ban
lists without having to worry about the lists changing under them.
Allow reload of a series of persisted ban specs in one go.
Drop the internal ban delimiters in the persistent ban lists, and
reload all the statements in one go.
Don't report ban_magic to the stevedores on insertion, but delay it
until ban compile.

Document the reason.
Fix bug in smp_baninfo causing duplicate ban entries.
Report BAN event persistence failures back to cache_ban.c
Add a facility to export a complete ban list to the stevedores. Call
this on startup, after reading the persisted ban lists, to make sure
all stevedores has all the bans from every stevedore stored.
Try to export the ban list on STV_BanInfo failures.

When STV_BanInfo fails, it means the stevedore has run out of space to
persist the list. An export should descrease the size.