I guess I forgot to test it after changing it to an Insert()

I'm totally not making fun of any social networks. Promise.

Who knew! (RFC 2616, 5.1.1)

For sendfile(2) support. I should really DRY up the implementations here...

In order to avoid a dependency on the go.crypto terminal package, let's try to
do our own TTY sniffing. I think in practice this will work surprisingly well,
even if it feels incredibly sketchy.

I've currently written three:
- Request ID generation
- Request logging, with color (!)
- Recovery from panics

Package web will now add a key to the environment when it fails to find a
valid route for the requested method, but when valid routes exist for other
methods.

This allows either the 404 handler or a sufficiently clever middleware layer to
provide support for OPTIONS automatically.

I have no idea if net/http does this for you already, but I may as well do it
myself too...

Add tests for both string and regular expression patterns. Also, reimplement
regexp.Regexp.Prefix() on top of the raw regexp/syntax representation, so we can
get a little more information out of regexps:
- Whether or not the regexp is left-anchored (at the beginning of the string)
- What the prefix of the regular expression is, even for left-anchored
  expressions.

We do this by running the regular expression instructions ourselves, more or
less cargo-culting the original implementation from package regexp/syntax.

Unfortunately it's ~impossible to make this abstraction non-leaky, because the
regexp package doesn't give us information about whether or not it was
constructed using POSIX or Perl syntax, for example, or if the longest-match
setting was applied.

The upshot is that regexps are now probably pretty performant-ish. Maybe. (I
haven't actually benchmarked it).

My tests caught some bugs! Amazing!

So I don't forget.

The idea is to make goji super easy to use out of the box.

They say that every programmer builds a web framework at some point. This one is
mine.

The basic idea behind this one is that I wanted a Sinatra for Go, and I couldn't
find one anywhere. Furthermore, net/http is in many ways really close to what I
want out of a Sinatra-in-Go, and many of the frameworks I did find seemed to
reinvent too much, or were incompatible with net/http in weird ways, or used too
much questionable reflection magic. So long story short, I wrote my own.

This implementation is only half-baked, and among other things it's missing a
whole lot of tests.

Apparently stdlib support will be in Go 1.3. Yay!

Package graceful provides graceful shutdown support for net/http servers,
net.Listeners and net.Conns. It does this through terrible, terrible hacks, but
"oh well!"

Signed-off-by: Ondrej Kupka <ondra.cap@gmail.com>

Add GetAll method (take two)

As kisielk just [told me](709e005f84 (commitcomment-3636470),) maps can be nil

GetAll returns all stored values for the request as a map.

Package bind provides a convenient syntax for binding to sockets, as well as a
fair bit of magic to automatically Do The Right Thing in both development and
production.

Package param implements parameter parsing into a target struct (in much the
same way as encoding/json parses JSON into a struct). It targets the common
jQuery.param / Ruby on Rails style parameter serialization format.

Also some philosophy. Because why not.

This is primarily needed to allow the test to run unmodified in certain
specialized environments (namely, Google's build clusters)