|
Hi James,
yes ok, but this setting is for all http connetion with the concept like that of the DataSource and the jdbc Connection,
you could have a specific setting for each endpoint to which you want to make a request and create the same metadata also for http and https connections.
By defining this datasource and connection pool of http connections on the application server, and the module that needs the connection requests it to the AS, which takes care of managing the connections, the pool and the authentication mechanisms.
Regards
Angelo Rubini
Da: rest-dev <rest-dev-bounces@xxxxxxxxxxx> per conto di James Perkins via rest-dev <rest-dev@xxxxxxxxxxx>
Inviato: giovedì 27 febbraio 2025 10:19
A: Jakarta Rest project developer discussions <rest-dev@xxxxxxxxxxx>
Cc: James Perkins <jperkins@xxxxxxxxxx>
Oggetto: Re: [rest-dev] Proposal: Create a set of interface, api to standardize http client and Http ConnetionPool
In either case, I don't think the Jakarta REST speci is a place to create an API like this. IMO if there was something wanted beyond the JDK HTTP Client, it should be a separate specification.
James R. Perkins
Principal Software Engineer
Red Hat
![]()
Hello everyone,
I recently posted a proposal to standardize interface/api for http/https client implementations and the possible pooling mechanism. Could it be a hook to leverage a standard API inside Jakarta RESTful Web Services that can also be leveraged by the standard MicroProfile Rest Client?
" into jdk-net channel 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
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?
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
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
|
