Paulex, I make HttpsURLConnection as a wrapper over the existing HttpURLConnection implementation (due to HTTPs spec: "Simply use HTTP over TLS precisely as you would use HTTP over TCP." RFC 2818). I.e. I do not reimplement HTTP functionality, just reuse it (although some minor updates of the base HttpURLConnection implementation should be made). So if there will be support for persistent connections in HttpURLConnection, HttpsURLConnection will have it too. But Http implementation uses plain sockets, while Https uses SSL sockets. Thus we should use whether 2 different connection pools (one for http, one for https) or indexing of sockets in the pool should be made by URL with non empty protocol part (i.e. "http://some.host/"; or "https://some.host/";) to distinguish http connections from https' ones.
Thanks, Alexander
