Proposal: Create a set of interface,api to standardize http client and Http ConnetionPool

[Angelo Rubini]

Hello everyone,

for a long time there have been various different implementations of clients to manage http and https connections as well as custom solutions,
 to manage the connection pools of the same http/https connections.

Wouldn't it be a good idea to standardize a set of interfaces and APIs as done for database connections with jdbc and datasource?
It's nice to have an interface similar to https://docs.oracle.com/javase/8/docs/api/javax/sql/DataSource.html for Http Connection and  ConnectionPool.

Proposal: Create a set of api,interface to standardize http clients (like internal jdk client, apache httpClient etc).
And also create, as done for jdbc, an example of an Interface as a DataSource: The DataSource interface is implemented by a driver vendor. There are three types of implementations:    1)Basic implementation -- produces a standard Connection object    2)Connection pooling implementation -- produces a Connection object that will automatically participate in connection pooling. This implementation works with a middle-tier connection pooling manager. to also have a standard for the creation and management of http connection pools.

How do you think?

Regards
Angelo Rubini

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/net-dev/attachments/20250226/b28eddf7/attachment.htm>