Explore >> Select a destination
|
You are here 
|
jbrandhorst.com | ||
| | | | |
konradreiche.com
|
|
| | | | | Starting a goroutine is as easy as adding the go keyword in front of a method, but managing the lifecycle of a goroutine is not. If you only need to start a few goroutines and wait for their completion, you are off the hook thanks to sync.WaitGroup. However, what if a goroutine has to run for a specific duration or repeatatly in a loop until the initiating code terminates? Does it matter? After all, if the main goroutine terminates, any other goroutine will also stop. It does matter, because depending on what the goroutines are doing, it might leave your system in an inconsistent or invalid state. Channels are a commonly used to signal to a goroutine that it can shut down, but I often see the use of a signaling channel, for example chan bool or chan struct{}... | |
| | | | |
pauladamsmith.com
|
|
| | | | | This is a simple and easily generalizable way to put an upper-bound on the maximum number of simultaneous clients to a Go net/http server or handler. The idea is to use a counting semaphore, modeled with a buffered channel, to cause new clients to... | |
| | | | |
blog.owulveryck.info
|
|
| | | | | This is a simple article that describes the wiring of the tool I made for streaming the content of the remarkable 2 on a computer. From the proc filesystem to the gRPC implementation over HTTP/2 via the certificate generation. | |
| | | | |
www.sethvargo.com
|
|
| | | Go 1.21 has some awesome new functionality that improves the developer experience and performance. | ||
