Upgrade to HttpCore 5.5 / Getting started guide - #45
Open
ok2c wants to merge 1 commit into
Open
Conversation
michael-o
requested changes
Aug 18, 2026
| times (unless their state can be reset). One must create a new instance for each new | ||
| message exchange execution. | ||
|
|
||
| One can use`AsyncClientPipeline` and `AsyncJsonClientPipeline` utility classes to simplify |
| message exchange execution. | ||
|
|
||
| One can use`AsyncClientPipeline` and `AsyncJsonClientPipeline` utility classes to simplify | ||
| assmbly of async message exchange handlers. |
| choosing the classic requester for use scenarios with the HTTP/2 protocol support being | ||
| optional. | ||
|
|
||
| Classic message exchange handlers can be state-less and they generally tend to have |
| processing based on predefined request route definitions. | ||
|
|
||
| Please note however HttpCore servers do not support advanced server features such as | ||
| different authentication schemes, access control and user rile management out of the box. |
| Please note async message exchange handlers are state-ful and cannot be executed multiple | ||
| times. One must create a new instance for each new message exchange execution. | ||
|
|
||
| One can use`AsyncServerPipeline` and `AsyncJsonServerPipeline` utility classes to simplify |
| times. One must create a new instance for each new message exchange execution. | ||
|
|
||
| One can use`AsyncServerPipeline` and `AsyncJsonServerPipeline` utility classes to simplify | ||
| assmbly of async message exchange handlers. |
| sides, does not need to handle requests with large or unexpected content body and support | ||
| thousands of concurrent connections. | ||
|
|
||
| Classic message exchange handlers can be state-less and they generally tend to have a |
| be used to plug-in custom logging. | ||
|
|
||
| HttpCore ships with `httpcore5-testing` module that provides a number of listener | ||
| implementations that log DEBUG priority events through `slfj4` facade. |
| be used to plug-in custom logging. | ||
|
|
||
| HttpCore ships with `httpcore5-testing` module that provides a number of listener | ||
| implementations that log DEBUG priority events through `slfj4` facade. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@arturobernalg @rschmitt @garydgregory @michael-o
Folks, I finally managed to put together some sort of document describing the intent & design objectives as well as as "getting started" guide for HttpCore. Please let me know if you find anything objectionable or wrong
@garydgregory Do feel free to correct my English as you deem appropriate
@rschmitt This is my attempt at explaining the initial motivation for HttpClient / HttpCore module split at the project's inception in November 2007. We can discuss if it still makes sense 20 years after. But this is how it all started.