spine-server-handlers

You create WebSocket JSON-RPC endpoints for Spine domains by building typed handlers with defined parameters and results, then registering them during server startup. This approach enforces standardized naming and predictable behavior across all domain operations.

Zod schema validation for WebSocket JSON-RPC 2.0 domain handlers works by enforcing structured request and response schemas for handler parameters and results. This standardizes validation across all Spine domain endpoints, ensuring predictable and testable behavior.

The best way to manage session context in WebSocket JSON-RPC servers is using session-aware context management to persist and reuse current project or structure state across multiple requests. This maintains consistent state throughout client interactions.

You handle errors in WebSocket JSON-RPC domain handlers by implementing a shared RpcError framework. This unified error scheme provides robust, structured error handling across all registered Spine domain endpoints.

You can rapidly add new domain endpoints to a WebSocket JSON-RPC server without breaking existing behavior by applying standardized handler registration patterns. Typed schemas and a unified RpcError framework ensure new endpoints remain predictable and testable.

Standardized handler naming for WebSocket JSON-RPC domain operations is needed to maintain consistency across multiple Spine domains. It enables rapid onboarding of new endpoints like character creation or structure tree operations with predictable routing.