Lakona.Rpc.Client 0.12.0

Lakona.Rpc.Client

Client runtime implementation for Lakona.Rpc.

Install

dotnet add package Lakona.Rpc.Client

Documentation

API reference: https://bruce48x.github.io/Lakona.Rpc/reference/api/

Generated RpcClient reference: https://bruce48x.github.io/Lakona.Rpc/reference/generated-client/

Design boundary: https://bruce48x.github.io/Lakona.Rpc/concepts/design-boundary/

Dependencies

• Lakona.Rpc.Core

Lakona.Rpc.Client has no hard dependency on concrete serializer or transport implementations.

Includes

• RpcClientOptions
• RpcClientRuntime
• notification diagnostics through UnhandledNotificationReceived and NotificationHandlerException

Recommended Entry

Lakona.Rpc.Client provides the transport-agnostic runtime building blocks. The user-facing RpcClient type is generated by Lakona.Rpc.Analyzers for each contract set.

Typical usage looks like this:

using Rpc.Generated;

var options = new RpcClientOptions(transport, serializer)
{
    KeepAlive = new RpcKeepAliveOptions
    {
        Enabled = true,
        Interval = TimeSpan.FromSeconds(15),
        Timeout = TimeSpan.FromSeconds(45)
    }
};

await using var client = new RpcClient(options);
await client.ConnectAsync(ct);

RpcClient.Api is generated per contract set and exposes grouped service clients after the connection is configured.

RpcClientRuntime and the generated RpcClient are single-use connection objects. After disconnecting or disposing, create a new transport, options object, and generated client for reconnect.

Server Notifications

Generated notification binders register one handler per notification method. Duplicate registration fails fast because notifications model a contract implementation, not a general event subscription list.

RpcClientRuntime accepts asynchronous notification handlers through Func<T, ValueTask>. Synchronous handlers can still use the convenience overload.

Notification handler exceptions do not disconnect the transport. Observe them through NotificationHandlerException. Server notification frames without a registered handler are reported through UnhandledNotificationReceived.

KeepAlive

RpcClientOptions.KeepAlive enables connection-level idle ping / pong and timeout detection.

• The client sends ping only when the connection is idle.
• Any inbound frame counts as activity and clears the pending timeout window.
• RpcClientRuntime exposes LastSendAt, LastReceiveAt, LastRtt, and TimedOutByKeepAlive for diagnostics.