Exactly the same code, just (hopefully) organized a little more
sensibly.

This change makes package graceful/listener track all connections that
have been Accepted, not just the ones considered idle. The motivation
here is to support a DrainAll function on graceful listeners, allowing
users an alternative to patiently waiting (potentially forever) for
in-use connections to become idle.

This has been fixed in v1.9.17 of App Engine:
https://code.google.com/p/googleappengine/issues/detail?id=11346

This reverts commit 9556e1736d.

Fixes #67.

It was exposed mostly for documentation of a Go 1.2 polyfill, and really
doesn't feel like it should be exposed long-term, since it hasn't done
anything in frightfully long.

This is a breaking change for advanced users of package graceful, for
which there is unfortunately no easy workaround (at least for Go 1.2
users, which are the ~only ones affected).

Go's regular expressions don't allow you to create a capturing group
named "*", which previously made using SubRouter with regular expression
patterns impossible. This change introduces the alternate key "_", which
happens to be a legal capturing group name.

Fixes #98.

This change addresses the POODLE vulnerability [0]. Unfortunately it
makes package graceful's behavior here slightly different than the stock
net/http methods of the same name, but I think that's fine in this
situation.

[0]: https://www.openssl.org/~bodo/ssl-poodle.pdf

Thanks to @ekanna for reporting this. Fixes #101.

This change refactors package graceful into two packages: one very well
tested package that deals with graceful shutdown of arbitrary
net.Listeners in the abstract, and one less-well-tested package that
works with the nitty-gritty details of net/http and signal handling.

This is a breaking API change for advanced users of package graceful:
the WrapConn function no longer exists. This shouldn't affect most users
or use cases.

In particular, these started failing when running tests under the race
detector in Go 1.4 [0], probably due to some kind of (GC?) hijinks
clearing out the sync.Pool.

[0]: these tests might have also failed in 1.3, but I didn't check

Closes #12

Closes #11

Breaking changes:
Changed from pointers to value arguments.
If this breaks your code, use latest stable v1 (tag:v1.1.0).
You could also use gopkg.in: go get http://gopkg.in/blang/semver.v1

Closes #10

Closes #9

Closes #8

Closes #7

Add Travis-ci tests build on Go version 1.3 / 1.4

Resolves #6

The goal here is to make it easy for people to write thin wrappers
around the built-in Patterns.

"util" is a really bad name for a package since it isn't very
descriptive and so often collides with other names.

Unfortunately, this is a breaking change, but it's both very easy to fix
and perhaps more importantly also better to do now than later.

Fixes #18

Prevent shutdown race, and refuse new requests.

This is pretty frustrating: it doesn't look like it's going to be easy
to get the "cover" tool to work across both 1.3 and 1.4, since they
aren't able to agree on where to install the tool from. I'm sure there's
a way to work around this, but in the meantime let's just disable
coverage testing entirely.

The official "cover" package has moved, and Go 1.4 will start enforcing
canonical imports.

use direct result of switch type assertion

Use range syntax

Remove signal.go logging; log from hook functions instead.

Previously, a route like "/:a.png" would match "/foo/bar/baz.png".
This was incorrect, as all matches should be restricted to path segments
(or smaller, as dictated by a break character).

This bug was introduced in 1a390aba1c.

Fixes #75.