I am building a command line app which needs to start its own HTTP server. My idea is to start the http server inside a goroutine in my main program like this:
func main() {
go myserver()
// perform lots of time-consuming tasks
}
func myserver() {
s := &http.Server{
Addr: ":8080",
Handler: MyHandler{},
}
log.Fatal(s.ListenAndServe())
}
ListenAndServe
method, there is no way of signalling via a sync.WaitGroup
or a channel.Are there other alternatives that are idiomatic to golang ?
When the main goroutine returns, the entire runtime system quits, rather abruptly. Hence any goroutines that are stuck waiting to send on an unbuffered or full channel simply ... cease to exist.
The answer is yes. If the function that calls a goroutine exits(returns) before the thread(goroutine) finishes.
A goroutine is a lightweight thread managed by the Go runtime.
Golang provides goroutines to support concurrency in Go. A goroutine is a function that executes simultaneously with other goroutines in a program and are lightweight threads managed by Go. A goroutine takes about 2kB of stack space to initialize.
If you are running the web interface until the program exits, you can just return from the main thread. Returning from the main thread exits the program even if another goroutine is working. If you want the main thread to send a kill to the http server, the best way is to close the listener.
func main() {
l, err := net.Listen("tcp", ":8080")
if err != nil {
log.Fatal(err)
}
go myserver(l)
// perform lots of time-consuming tasks
l.Close()
}
func myserver(l net.Listener) {
s := &http.Server{
Addr: ":8080",
Handler: MyHandler{},
}
log.Print(s.Serve(l))
}
This will not close connections already open. It will only prevent new ones from being created. You need to add logic to your handler and/or stop keep-alives to ensure that the connection isn't reused for long after you kill listener.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With