Connections form the foundaton of the client-server relationship. For every WebSocket the cable server is accepting, a Connection object will be instantiated. This instance becomes the parent of all the channel subscriptions that are created from there on. The Connection itself does not deal with any specific application logic beyond authentication and authorization. The client of a WebSocket connection is called the consumer. A single consumer may have multiple WebSockets open to your application if they use multiple browser tabs or devices.