Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rest-dev] [External] : Re: Proposal: Create a set of interface, api to standardize http client and Http ConnetionPool
  • From: Santiago Pericasgeertsen <santiago.pericasgeertsen@xxxxxxxxxx>
  • Date: Fri, 28 Feb 2025 14:36:16 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oracle.com; dmarc=pass action=none header.from=oracle.com; dkim=pass header.d=oracle.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=pr85uuRcO0VymWSNgp6hAvsPRNJoWP56fWaAcgieB9c=; b=qWauDJxXnOP02IWpThidKEpvKTMUqSTMlk3r89e7hD+shTWXJGQf3/s9PDEd6t6lWD2vs5xL/jeO4d2vQELf1hIFXCWUzKiCZGVpeqL6MbFse1NrwguyZVrEhx/SUvGv0d0N5fmxaDf3QIX/uInCw3e6ucDjq7dUoBvwiAG7rhPtO1qv2JxnC12Y9lunbEDdV4aa3lkv+2mI1uOJv8jgcBvU/IpB23g/qzvWB4RJ31kYCxaQ/cmHW18RpFq/zFPUrZb8vCv2s3D7tGPU7WG5Xn09Tj0qURM8iwsChMTa5OxhOwNxGQI9ka7bYvoaH7k3jZZFUK375se2BlgPhEGWZg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=hbiqNIOVR1HzQOGDh/IWl7e5mc0kUar9NTn2Y68kHxKg5WoWWLtBf4b3yrH8hsoL6q9g20KLZQFAM2XlH5lXAqKD33dDBy3yAaIfwrOc5CTdN8o/NjOULrBLyR94yF3mak8BQ0GTMS8POP/aEbyXmP6NcooTDS4k36+VAya39zAOENFCP2ccuH64LBGCRsGjqaQ0njsPvvlu40O7qgAd4em0Ykwd2Vmyo9FaWMkj3A+Cv+xp+XE6AAtSsx1c2TWULEF4o1RRbWRlkYWk+W9GfYk+H13XU7yqWA71/qVokE6RVX6DvEerDBn4P6oVSAxDCyLQaqR6VO7wzBmxrIxqJQ==
  • Delivered-to: rest-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/rest-dev/>
  • List-help: <mailto:rest-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/rest-dev>, <mailto:rest-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/rest-dev>, <mailto:rest-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHbiV1Yy1pdo8VjXkmMfRJz9QzIRLNcyXeA
  • Thread-topic: [External] : Re: [rest-dev] Proposal: Create a set of interface, api to standardize http client and Http ConnetionPool



On Feb 27, 2025, at 4:19 PM, James Perkins via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

Is there a reason the JDK HTTP Client doesn't work for this? https://docs.oracle.com/en/java/javase/21/docs/api/java.net.http/module-summary.html

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.

 +1

— Santiago


James R. Perkins

Principal Software Engineer

Red Hat



On Wed, Feb 26, 2025 at 5:11 AM Angelo Rubini via rest-dev <rest-dev@xxxxxxxxxxx> wrote:
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



Da: Angelo Rubini <angelorubini@xxxxxxxxxx>
Inviato: mercoledì 26 febbraio 2025 10:14
A: net-dev@xxxxxxxxxxx <net-dev@xxxxxxxxxxx>
Oggetto: Proposal: Create a set of interface,api to standardize http client and Http ConnetionPool
 
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

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://accounts.eclipse.org__;!!ACWV5N9M2RV99hQ!NE2sYOAM1sJVJQSgV3wHUhZrXgKbm8uDQCvQcbiBHtd9-Io9exjFRzioBVzdaVtFlcmvrQOJLTW8aRKtDFuoeMqXV3ht$


Back to the top