diff options
| author | Andre Weissflog <floooh@gmail.com> | 2024-10-16 11:17:58 +0200 |
|---|---|---|
| committer | Andre Weissflog <floooh@gmail.com> | 2024-10-16 11:17:58 +0200 |
| commit | 4bda1469d3b311af03a34dd956460776c920dc2e (patch) | |
| tree | 57b2c3c5d1cd3ee206e9b91d89870d13eb28727b /sokol_fetch.h | |
| parent | 72de62c89c56502c1af9710641a60d8cae94a21e (diff) | |
fix a couple of documentation typos
Diffstat (limited to 'sokol_fetch.h')
| -rw-r--r-- | sokol_fetch.h | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/sokol_fetch.h b/sokol_fetch.h index 2cc49312..d2f989ae 100644 --- a/sokol_fetch.h +++ b/sokol_fetch.h @@ -498,7 +498,7 @@ After the user callback returns, and all file data has been loaded (response.finished flag is set) the request has reached its end-of-life - and will recycled. + and will be recycled. Otherwise, if there's still data to load (because streaming was requested by providing a non-zero request.chunk_size), the request @@ -610,7 +610,7 @@ without downloading the entire file first (the Content-Length response header only provides the compressed size). Furthermore, for HTTP range-requests, the range is given on the compressed data, not the - uncompressed data. So if the web server decides to server the data + uncompressed data. So if the web server decides to serve the data compressed, the content-length and range-request parameters don't correspond to the uncompressed data that's arriving in the sokol-fetch buffers, and there's no way from JS or WASM to either force uncompressed @@ -671,7 +671,7 @@ When a request is sent to a channel via sfetch_send(), a "free lane" will be picked and assigned to the request. The request will occupy this lane for its entire life time (also while it is paused). If all lanes of a - channel are currently occupied, new requests will need to wait until a + channel are currently occupied, new requests will wait until a lane becomes unoccupied. Since the number of channels and lanes is known upfront, it is guaranteed @@ -800,7 +800,7 @@ On platforms with threading support, each channel runs on its own thread, but this is mainly an implementation detail to work around - the blocking traditional file IO functions, not for performance reasons. + the traditional blocking file IO functions, not for performance reasons. MEMORY ALLOCATION OVERRIDE |