Currently, the client polls the server for new status & console content. The default polling period is 3 seconds for console content. Our IT group notes this design produces a high demand (ca. ~30k/day for each client) by the client for DNS requests for the server's FQDN.
Other web clients (such as GitHub & Slack) employ some mechanism where the server advises the client of new information. Presumable, this is enabled on initial connection by creating a dedicated and persistent web socket through which such communications occur.
How can we gain such server-side push of status and content without need for polling by the client?
Currently, the client polls the server for new status & console content. The default polling period is 3 seconds for console content. Our IT group notes this design produces a high demand (ca. ~30k/day for each client) by the client for DNS requests for the server's FQDN.
Other web clients (such as GitHub & Slack) employ some mechanism where the server advises the client of new information. Presumable, this is enabled on initial connection by creating a dedicated and persistent web socket through which such communications occur.
How can we gain such server-side push of status and content without need for polling by the client?