Close a WebSocket when it is idle

[ikhoon]

Because WebSocket is mostly a long-running request, it is not easy to limit when it will end with a request timeout. It would make more sense to terminate the request when no messages are sent or received for a certain period of time.

The existing idle timeout handler operates at the connection level so a new scheduler that can perform at the WebSocket level is necessary.