Lakona.Rpc.Server
0.12.1
dotnet add package Lakona.Rpc.Server --version 0.12.1
NuGet\Install-Package Lakona.Rpc.Server -Version 0.12.1
<PackageReference Include="Lakona.Rpc.Server" Version="0.12.1" />
<PackageVersion Include="Lakona.Rpc.Server" Version="0.12.1" />
<PackageReference Include="Lakona.Rpc.Server" />
paket add Lakona.Rpc.Server --version 0.12.1
#r "nuget: Lakona.Rpc.Server, 0.12.1"
#:package Lakona.Rpc.Server@0.12.1
#addin nuget:?package=Lakona.Rpc.Server&version=0.12.1
#tool nuget:?package=Lakona.Rpc.Server&version=0.12.1
Lakona.Rpc.Server
Server runtime implementation for Lakona.Rpc.
Install
dotnet add package Lakona.Rpc.Server
Documentation
API reference: https://bruce48x.github.io/Lakona.Rpc/reference/api/
Design boundary: https://bruce48x.github.io/Lakona.Rpc/concepts/design-boundary/
Dependencies
Lakona.Rpc.Core
Lakona.Rpc.Server has no hard dependency on concrete serializer or transport implementations.
Includes
RpcServerHostBuilderRpcServerHostRpcGeneratedServiceBinder- runtime dispatch infrastructure used by generated service binders
Recommended Usage
Use RpcServerHostBuilder to compose serializer, transport, generated binders, and security in one place:
var builder = RpcServerHostBuilder.Create()
.UseCommandLine(args)
.UseSerializer(new MemoryPackRpcSerializer())
.UseKeepAlive(TimeSpan.FromSeconds(15), TimeSpan.FromSeconds(45))
.UseAcceptor(new TcpConnectionAcceptor(20000));
await builder.RunAsync();
When the entry assembly contains code-generated AllServicesBinder, the builder binds it automatically.
Extension Boundary
Server applications should not create RpcSession directly or hand-write (serviceId, methodId) handler dictionaries. RpcSession, RpcServiceRegistry, and low-level handler delegates are runtime implementation and generated-binder support APIs.
Custom transports and serializers are supported extension points. Implement ITransport, IRpcConnectionAcceptor, or IRpcSerializer, then pass those implementations into RpcServerHostBuilder.
KeepAlive
RpcServerHostBuilder.UseKeepAlive(...) enables connection-level idle timeout handling for accepted sessions.
- The server automatically replies to client keepalive pings with pong.
- When enabled on the host, each accepted connection also tracks idle time and disconnects sessions that remain inactive longer than the configured timeout.
Authentication And Authorization Boundary
Lakona.Rpc.Server is focused on RPC session management, transport integration, request dispatch, and connection-level concerns such as framing, keepalive, and transport security.
Request-level authorization is not built into the server runtime by design.
See the canonical design boundary page for the production integration boundary:
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Lakona.Rpc.Core (>= 0.12.0)
- Microsoft.Extensions.Logging.Console (>= 10.0.8)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Lakona.Rpc.Server:
| Package | Downloads |
|---|---|
|
Lakona.Game.Cluster.Rpc
Lakona.Rpc-based node messenger adapter for Lakona.Game cluster routing. |
|
|
Lakona.Game.Server
Server-side actor runtime, RPC hosting helpers, session lifecycle, and reliable push infrastructure for Lakona.Game applications. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.12.1 | 0 | 6/7/2026 |