61175ef091
- over the course of a project history every maintainer needs to update
its dependency packages, the problem essentially with godep is manipulating
GOPATH - this manipulation leads to static objects created at different locations
which end up conflicting with the overall functionality of golang.
This also leads to broken builds. There is no easier way out of this other than
asking developers to do 'godep restore' all the time. Which perhaps as a practice
doesn't sound like a clean solution. On the other hand 'godep restore' has its own
set of problems.
- govendor is a right tool but a stop gap tool until we wait for golangs official
1.5 version which fixes this vendoring issue once and for all.
- govendor provides consistency in terms of how import paths should be handled unlike
manipulation GOPATH.
This has advantages
- no more compiled objects being referenced in GOPATH and build time GOPATH
manging which leads to conflicts.
- proper import paths referencing the exact package a project is dependent on.
govendor is simple and provides the minimal necessary tooling to achieve this.
For now this is the right solution.
|
||
|---|---|---|
| .. | ||
| httpdown.go | ||
| license | ||
| patents | ||
| readme.md | ||
httpdown 
Documentation: https://godoc.org/github.com/facebookgo/httpdown
Package httpdown provides a library that makes it easy to build a HTTP server that can be shutdown gracefully (that is, without dropping any connections).
If you want graceful restart and not just graceful shutdown, look at the grace package which uses this package underneath but also provides graceful restart.
Usage
Demo HTTP Server with graceful termination: https://github.com/facebookgo/httpdown/blob/master/httpdown_example/main.go
-
Install the demo application
go get github.com/facebookgo/httpdown/httpdown_example -
Start it in the first terminal
httpdown_exampleThis will output something like:
2014/11/18 21:57:50 serving on http://127.0.0.1:8080/ with pid 17 -
In a second terminal start a slow HTTP request
curl 'http://localhost:8080/?duration=20s' -
In a third terminal trigger a graceful shutdown (using the pid from your output):
kill -TERM 17
This will demonstrate that the slow request was served before the server was
shutdown. You could also have used Ctrl-C instead of kill as the example
application triggers graceful shutdown on TERM or INT signals.