3 ms·
> Having a way of enumerating different states of the application, and jumping between those states (URIs) is just one. Most web apps treat different routes as
by barrkel 11y ago
> Having a way of enumerating different states of the application, and jumping between those states (URIs) is just one.
Most web apps treat different routes as different screens, effectively, to use a piece of jargon from a bygone time. A URI is usually just a parameterized screen; IDs in the URI determine which bits of data the app is viewing / editing, no more or less than parameters to a Visual Basic or Delphi form.