-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
feat(ext/http): Make http server parameters configurable #26785
Merged
magurotuna
merged 3 commits into
denoland:main
from
magurotuna:magurotuna/deno-http-configurable-http2-params-2
Nov 19, 2024
Merged
feat(ext/http): Make http server parameters configurable #26785
magurotuna
merged 3 commits into
denoland:main
from
magurotuna:magurotuna/deno-http-configurable-http2-params-2
Nov 19, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
magurotuna
force-pushed
the
magurotuna/deno-http-configurable-http2-params-2
branch
from
November 8, 2024 07:34
f758077
to
d207425
Compare
satyarohith
reviewed
Nov 14, 2024
magurotuna
changed the title
feat(ext/http): Make http2 parameters configurable
feat(ext/http): Make http parameters configurable
Nov 18, 2024
magurotuna
changed the title
feat(ext/http): Make http parameters configurable
feat(ext/http): Make http server parameters configurable
Nov 18, 2024
satyarohith
approved these changes
Nov 18, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
magurotuna
deleted the
magurotuna/deno-http-configurable-http2-params-2
branch
November 19, 2024 01:46
magurotuna
added a commit
that referenced
this pull request
Nov 19, 2024
This commit makes HTTP client parameters used in `fetch` API configurable on the extension initialization via a callback `client_builder_hook` that users can provide. The main motivation behind this change is to allow `deno_fetch` users to tune the HTTP/2 client to suit their needs, although Deno CLI users will not benefit from it as no JavaScript interface is exposed to set these parameters currently. It is up to users whether to provide a hook function. If not provided, the default configuration from hyper crate will be used. Ref #26785
magurotuna
added a commit
to magurotuna/deno
that referenced
this pull request
Nov 19, 2024
…26909) This commit makes HTTP client parameters used in `fetch` API configurable on the extension initialization via a callback `client_builder_hook` that users can provide. The main motivation behind this change is to allow `deno_fetch` users to tune the HTTP/2 client to suit their needs, although Deno CLI users will not benefit from it as no JavaScript interface is exposed to set these parameters currently. It is up to users whether to provide a hook function. If not provided, the default configuration from hyper crate will be used. Ref denoland#26785
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit makes http server parameters configurable on the extension initialization via two callbacks users can provide.
The main motivation behind this change is to allow
deno_http
users to tune the HTTP/2 server to suit their needs, although Deno CLI users will not benefit from it as no JavaScript interface is exposed to set these parameters currently.It is up to users whether to provide hook functions. If not provided, the default configuration from hyper crate will be used.