romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-08-24 16:33:33 +03:00
Code Issues Projects Releases Packages Wiki Activity

docs: fixup wording nits

Browse source 
Mostly sentences starting with bad words
This commit is contained in:
Daniel Stenberg 2026-03-09 16:31:37 +01:00
parent 713287188e
commit 8ec0e1e109
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
10 changed files with 28 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/internals/CONNECTION-FILTERS.md
View file

@ -123,14 +123,14 @@ The filter type `cft` is a singleton, one static struct for each type of
filter. The `ctx` is where a filter holds its specific data. That varies by
filter type. An http-proxy filter keeps the ongoing state of the CONNECT here,
free it after its has been established. The SSL filter keeps the `SSL*` (if
OpenSSL is used) here until the connection is closed. So, this varies.
OpenSSL is used) here until the connection is closed. This varies.
`conn` is a reference to the connection this filter belongs to, so nothing
extra besides the pointer itself.
Several things, that before were kept in `struct connectdata`, now goes into
the `filter->ctx` *when needed*. So, the memory footprint for connections that
do *not* use an http proxy, or socks, or https is lower.
the `filter->ctx` *when needed*. The memory footprint for connections that do
*not* use an http proxy, or socks, or https is lower.
As to transfer efficiency, writing and reading through a filter comes at near
zero cost *if the filter does not transform the data*. An http proxy or socks

2
docs/internals/MULTI-EV.md
View file

@ -115,7 +115,7 @@ in the middle of things. Also, a transfer might be interested in several
sockets at the same time (resolving, eye balling, ftp are all examples of
those).
### And Come Again
### Come Again
While transfer and connection identifiers are practically unique in a libcurl
application, sockets are not. Operating systems are keen on reusing their

4
docs/internals/TIME-KEEPING.md
View file

@ -18,8 +18,8 @@ passed a pointer to the `struct curltime now` to functions to save them the
calls. Passing this pointer down to all functions possibly involved was not
done as this pollutes the internal APIs.
So, some functions continued to call `curlx_now()` on their own while others
used the passed pointer *to a timestamp in the past*. This led to a transfer
Some functions continued to call `curlx_now()` on their own while others used
the passed pointer *to a timestamp in the past*. This led to a transfer
experiencing *jumps* in time, reversing cause and effect. On fast systems,
this was mostly not noticeable. On slow machines or in CI, this led to rare
and annoying test failures.