effect-rpc-client

Call RpcClient.make with your RpcGroup to get an object with one typed method per rpc tag. Provide a Protocol layer, any required client middleware layers, and a Scope, typically by wrapping it in Layer.effect inside a Context.Service.

Raw TCP requires a framed codec like ndjson, msgpack, or ndJsonRpc because plain json cannot find message boundaries. WebSocket works with any codec, and HTTP streaming responses need a framed codec so chunks arrive incrementally.

Use RpcTest.makeClient, which wires an in-process client and server through the real request, streaming, and middleware machinery with no transport. Provide the handler layers plus any server and client middleware layers, and the error channel excludes transport errors.

Header names are normalized to lowercase by Headers.fromInput, so sending { userId: '123' } arrives as headers.userid on the server. Server middleware must read the lowercase key.

Yes, the socket protocol retries with an exponential schedule capped at 5 seconds forever by default, and sends pings every 5 seconds. In-flight requests fail on connection errors unless retryTransientErrors is enabled, and requests are not replayed after reconnect.

RpcClientError represents transport failures such as socket errors, HTTP errors, or worker failures, separate from your declared rpc errors. Catch domain errors by tag and retry RpcClientError separately, excluding the RpcClientDefect reason which indicates a protocol bug.