tracker issue : CF-4199375

select a category, or use search below
(searches all categories and all time range)
Title:

Ability to keep connection state on http/s calls

| View in Tracker

Status/Resolution/Reason: To Fix//EnhancementRequired

Reporter/Name(from Bugbase): Luis Majano / Luis Majano ()

Created: 07/28/2017

Components: Net Protocols

Versions: 2016

Failure Type: Others

Found In Build/Fixed In Build: /

Priority/Frequency: Normal /

Locale/System: / Core

Vote Count: 5

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

Attachments:

Comments:

Please note that Lucee has implemented this already
Comment by Luis M.
481 | July 28, 2017 03:15:34 PM GMT
+1 think this would be great when you need to do lots of RESTful calls to 3rd party services.
Vote by John W.
484 | July 28, 2017 03:51:57 PM GMT
Please note, Lucee has already implemented this feature. Please match their implementation or frameworks won't be able to use it. https://luceeserver.atlassian.net/browse/LDEV-1000
Comment by Bradley W.
482 | July 28, 2017 05:10:42 PM GMT
+1 ...........
Vote by Aaron N.
485 | July 28, 2017 08:54:53 PM GMT
Also filed CF-3039574 to optionally maintain session across cfhttp requests. Thanks!, -Aaron
Comment by Aaron N.
483 | July 29, 2017 08:32:39 AM GMT