Repository navigation
Gaoxy 0.13.0
Native WebSock connections default to persistent connections without frame-size,
message-size, fragment-count, callback-batch-count, inactivity or absolute-lifetime
ceilings. Explicit application limits remain supported. Generic service byte and
state budgets no longer cap retained WebSocket messages or callback state;
transport staging, queues and protocol windows stay finite and reusable.
The WebSock API still delivers complete messages, so memory grows with the
message, application state and pending output. Applications that produce data
independently need their own production policy. Protocol validation and mandatory
control-frame limits remain enforced. Callback execution, bounded writes and
normal close retain separate finite deadlines; an operation deadline does not
cover an entire progressing message or output batch.
Phoenix applications must explicitly configure
websocket: [timeout: :infinity] on their socket declarations to obtain
persistent connections. Authentication, Origin checks, heartbeats and deliberate
application close policies remain under application control. The separately
configured message-level Gaoxy.Proxy.WebSocket bridge retains its own policies.
See the capacity and configuration guide.
The H1/H2/H3 persistence goal uses infinite H1 reads after upgrade, H2 owner idle
suspension while WebSockets exist with restoration after the final WebSocket,
and H3 local idle suspension with keepalive below a finite peer idle period.
Hell 0.1.3 supplies the released public Hell.Handler.set_read_timeout/2 API
required for H2. Focused regressions verify quiet persistence, repeated exact
transfers, HTTP siblings, final-owner idle restoration and preservation of finite
partial-frame and explicit application lifetime deadlines.
HTTP/2 startup now treats a confirmed peer closure as a normal stop when setting
TCP/TLS receive options races with disconnect. Bare and SSL-wrapped failures
require confirmation through the supported socket API; live-peer option failures
retain their original error disposition. See the
issue #17 acceptance record.
The dependency cohort includes Hell 0.1.3, Abyss 0.10.0 and the HTTP/TLS/QUIC
packages at 0.21.17. The direct http_core requirement now has a 0.21.17 floor.
Plug.Crypto advances to 2.2.1. All six Hex distributions and the standalone
application use version 0.13.0.
Historical failures and specialist abnormal, slow-peer, pressure and
sustained-load qualification keep their recorded dispositions. See the
issue #16 qualification.