I think there a confusion of what I am trying to say. With the go routine
approach there is cost of 1M connections + cost of 1M go routines running a
blocking call all the time. With an event based system where I can
multiplex code execution over a fixed size go routines, the cost is already
cu
On Thu, Jan 5, 2017 at 9:51 AM, wrote:
> Hey guys,
>
> So for some time now I have been trying to build a high performance Pub/Sub
> server in Go. I am using gorilla websocket library, which in it self has a
> Read, Write methods
> (https://godoc.org/github.com/gorilla/websocket#Conn.ReadMessage
