Re:Goroutines, Nonblocking I/O, and Memory Usage
by neild on Thursday January 05, 2017 @06:55PM
(#13332635)
It's a standard library limitation.
One could imagine a function that takes a set of net.Conns and returns the ones that are available for reading. You'd then pass those off to a goroutine for processing with blocking I/O as usual.
One could imagine a function that takes a set of net.Conns and returns the ones that are available for reading. You'd then pass those off to a goroutine for processing with blocking I/O as usual.