Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow a pre-initalized HTTP client to be passed in the client builder #117

Merged
merged 2 commits into from
Feb 9, 2024
Merged

Conversation

SamuelYvon
Copy link
Contributor

This PR allows a user to re-use an HTTP client to back a soap client. This can be meaningful when trying limit the amount of outstanding connections taken by each client's connection pool.

I also modified the accessor of the auth module:

-pub(crate) mod digest;
-pub(crate) mod username_token;
+pub mod digest;
+pub mod username_token;

You cleverly allowed the transport to be a generic, so users are free to re-implement their client as they want, but not providing the auth crates mean they have to re-implement everything. This aims to make it a bit more flexible.

This PR allows a user to re-use an HTTP client to back a soap client.
This can be meaningful when trying limit the amount of outstanding
connections taken by each client's connection pool.

I also modified the accessor of the auth module:

```diff
-pub(crate) mod digest;
-pub(crate) mod username_token;
+pub mod digest;
+pub mod username_token;
```

You cleverly allowed the transport to be a generic, so users are free to
re-implement their client as they want, but not providing the auth
crates mean they have to re-implement everything. This aims to make
it a bit more flexible.
@DmitrySamoylov DmitrySamoylov merged commit 49c3f06 into lumeohq:main Feb 9, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants