This enhancement idea comes from the inherent nature of building apps as microservices. The initial handshakes between services using http or https is cpu and latency intensive. This is seen when making enough cfhttp calls in an application.
I would suggest a way to keep state on the connection with an appropriate timeout. This way, you can have one initial negotiation handshake and then subsequent calls can already use this connection tunnel and pay no penalty on creation of another connection.
I would suggest two new arguments for this feature:
* keepstate
* stateTimeout