Drive the responding side and install inbound lifecycle callbacks.
OptionalonMessage: OnWireMessageOptionalonDone: OnWireDoneAwait queued outbound delivery after requesting a half-close.
Return the normalized epoch deadline, or null when disabled.
Return the headers that will be, or were, sent on HTTP requests.
Return connect-response headers after they arrive, otherwise null.
Return the transport-assigned stream identifier.
Return an advanced transport handle, when the implementation has one.
Return the current terminal error, or OK while healthy/cleanly done.
Return peer half-close trailers once received.
Stop sending after queued messages, while continuing to receive.
Optionaltrailers: ByteMapInputQueue a message for asynchronous transport; this does not await delivery.
Change the absolute deadline; omit it to disable the deadline.
Optionaldeadline: WireDeadlineReplace request headers before start; headers then become fixed.
Drive the initiating side and install inbound lifecycle callbacks.
OptionalonMessage: OnWireMessageOptionalonDone: OnWireDoneAwait full stream completion rather than only the startup handshake.
Await connect response headers or the transport failure that prevented them.
StaticcreateConfigure a client without issuing the connect request yet.
Fetch-based client for A11's Server-Sent Events transport.
Because it uses
fetch, the transport negotiates HTTP/1.1 or HTTP/2 transparently (per the platform and ALPN): it works against an A11 native server serving SSE over either protocol, including HTTP/1.1 chunked transfer-encoding when the server'senable_http1option is on.The long-lived connect response carries messages from the service as SSE events; separate POST requests carry client messages back to the assigned stream id. The class still presents the ordinary WireStream lifecycle, so sessions and actions do not need to know that each direction uses a different HTTP request.
This is a client-only transport: call start, not accept. Wait for waitForHttpHeaders before reading response metadata. A normal shutdown still requires halfClose, drainOutgoingMessages, and eventual peer termination.