forked from curl/everything-curl
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
52 additions
and
7 deletions.
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# Backends | ||
|
||
A backend in curl is a **build-time selectable alternative implementation**. | ||
|
||
When you build curl, you can select alternative implementations for several | ||
different things. Different providers of the same feature set. You select | ||
which backend or backends (plural) to use when you build curl. | ||
|
||
- Backends are selectable and deselectable | ||
- Often platform dependent | ||
- Can differ in features | ||
- Can differ in 3rd party licenses | ||
- Can differ in maturity | ||
- The internal APIs are never exposed externally | ||
|
||
## Different backends | ||
|
||
In the libcurl source code, there are internal APIs for providing | ||
functionlity. In these different areas there are multiple different providers: | ||
|
||
1. IDN | ||
2. Name resolving | ||
3. TLS | ||
4. SSH | ||
5. HTTP/1 and HTTP/2 | ||
6. HTTP/3 | ||
7. HTTP content encoding | ||
|
||
## Backends visualized | ||
|
||
![libcurl backends](slide-libcurl-backends.jpg) | ||
|
||
Applications (in the upper yellow cloud) access libcurl through the public | ||
API. The API is fixed and stable. | ||
|
||
Internally, the "core" of libcurl uses internal APIs to perform the different | ||
duties it needs to do. Each of these internal APIs are powered by alternative | ||
implementations, in many times powered by different third party libraries. | ||
|
||
The image above shows the different third party libraries powering different | ||
internal APIs. The purple boxes are "one or more" and the dark grey ones are | ||
"one of these". |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.