In previous release the remote consoles functionality spawned a proxy process for each web socket client (opened console).
In Darga, there's a single websocket proxy process -- the websocket server role/worker that does the proxying for all the opened consoles.
The websocket worker also might be used for UI notifications about anync tasks happening.
One goal of the websocket worker is to support the remote consoles in more complicated network topologies and setups such as multiple isolated zones for different ManageIQ roles and hypervisors or front-end HA proxies.
For Darga, having a single proxy process also allowed us to bind that process to a single port and together with proxying that port through Apache on 443 we could greatly simplify the setup of SSL certificates for the remote consoles to work.