Why two (or three) go routines per connection? Why not one net socket (for reads...

lenkite · on Nov 23, 2017

Please upvote parent. This is the first thing that struck my mind too. golang offers `select` for non-blocking calls. Deeply skeptical that node.js is the best solution for a chat service. (unless the backend is serving rendered UI's)

Thetawaves · on Nov 24, 2017

You generally need one thread to read for incoming messages, typical:

  for {
      select {
      case <-finish:
          done <- true
          return
      default:
          // read from the socket
      }
  }

You need another thread to listen for messages on a channel and send them out the socket typical:

  for {
      select {
      case <-finish:
          done <- true
          return
      case msg <- msg_out:
          // write msg to socket

      }
  }

tankenmate · on Nov 24, 2017

Instead of?

  for {
    select {
    case <-finish:
      done <- true
      return
    case msg <- msg_out:
      // write handling
    case <-pubsub:
      // handle oob controls
    default:
      // read handling
    }
  }

Thetawaves · on Dec 7, 2017

You wont be able to write messages while blocked on the read in this scenario.