hn.today

Show HN: Durable Actor Session Protocol

dasp-protocol.github.io17 points7 comments
Screenshot of Show HN: Durable Actor Session Protocol

DASP defines a server protocol for "durable actor" sessions that let clients send commands, read saved state and outcomes, and disconnect and reconnect without losing progress. It uses five lightweight operations to open a session, submit commands, read views, fetch missed updates, and check command outcomes, so web apps, CLIs, and services share one actor session through the server. The protocol treats the server as the authoritative history: every accepted command gets a saved admission and an acceptance receipt, while the final outcome is stored separately; if effects cannot be firmly established the outcome is marked uncertain. Clients use stable command IDs to retry safely, and the server records progress so temporary in-progress state does not substitute for saved outcomes.

The protocol preserves an ordered update history and per-client cursor positions so returning clients resume from the last applied update. Shared sessions expose a single ordered timeline with independent cursors for each client, ensuring consistent replay and ordering across multiple participants. Implementations supply transport and storage; experimental native clients and bindings are provided for Elixir and TypeScript that follow the same wire contract. The draft emphasizes clear recovery rules, command admission semantics, and a minimal message set to support durable, reconnectable actor workflows.

Read on dasp-protocol.github.io7 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Web

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.