puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-11-03 23:23:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(transport): preserve native admission and pace file writes

Browse Source 
Sockets without a drain signal retain single-frame outbound admission while accepting chunked responses. Uploads and response-bearing control sends must observe queued admission failures instead of waiting for a response that cannot arrive.
This commit is contained in:
Mohamed Boudra
2026-10-30 17:41:57 +01:00
parent cacf186a94
commit b044201f62
12 changed files with 319 additions and 122 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/protocol-compatibility.md
+3 -2
View File
@@ -75,8 +75,9 @@ The framing module never selects an encryption construction.
Native uploads retain the platform's existing queue limits. React Native's
WebSocket does not report its queued bytes, so the client cannot wait for native
drain. Android's installed OkHttp transport closes when a send would put more
than 16 MiB in its queue. Negotiating chunking does not establish large native
upload support; daemon-to-native responses still use the daemon's paced writes.
than 16 MiB in its queue. The native transport disables outbound chunking, including
on routed channels, and retains its existing single-frame admission errors.
Inbound chunking remains enabled; daemon-to-native responses use the daemon's paced writes.
## Owned observations