Investigate the current OkHttp usage in route server communication, focusing on connection pool settings. Look at the route module's HTTP client configuration and determine if swapping to a long lived connection (e.g., WebSocket or HTTP/2) is feasible. The maintainer has not provided additional context, so examine the source code in the cim repository for relevant files.
