Server
Riot’s server story matters because many users eventually want to build a network-facing application, not just a command-line package.
This page is the high-level entrypoint to that story.
What this page should help you answer
Section titled “What this page should help you answer”- can Riot support the kind of server I want to build?
- what is the high-level model?
- when is the HTTP-level surface enough?
- when do I need to drop to TCP or UDP?
Those are adoption questions, not internal architecture questions.
The useful mental model
Section titled “The useful mental model”Think in layers:
- server-level concerns such as routing, requests, responses, and operational boundaries
- lower-level transport concerns such as sockets and streams
If you are building an HTTP service, start here. If you are building a protocol or a transport-level tool, move to TCP or UDP.
Why this page exists
Section titled “Why this page exists”A docs site like this should not force users to discover networking capability by accident through raw API docs.
There needs to be a page that says:
- yes, Riot has a server story
- here is the right starting layer
- here is how to go deeper when needed