The idea here was to zoom in on a very specific question: how does application state relate to the URL? Not the whole universe of state in an app, just the part where the URL has a role in carrying, pointing to, or ignoring state entirely.
When the server handles a request, it combines state from different sources: the URL, cookies, headers, and whatever state it keeps internally on its side. On the client, there can also be local UI state, but that never leaves the client unless explicitly sent. So the table is really about the URL’s role among those sources, not about state everywhere.
After thinking through the possibilities, it turns out there are only three patterns for how URLs can participate:
- The URL contains some of the state directly
(for example filters, pagination, search parameters) - The URL contains a token that points to state stored elsewhere on the server
(often called “deep linking” in Datastar conversations)