Originally posted by Ulf Dittmer:
The point of a connection pool is to leave connections open, e.g. to a DB server. Since HTTP is a connection-less protocol (meaning connection are closed as soon the transmission is done), the concept of pools doesn't apply here. (Yes, there's such a thing as HTTP keep-alive, but it still closes connections after a short time).
Using HTTPS instead of HTTP doesn't change this.
A new HTTP connection is fine as long as I can use the same SSL channels
over and over for many different HTTP connections.
HTTP connection is cheap, and SSL connection is expensive. It is why we want to pool SSL connection between HTTP server and App server.