|
|
|
|
|
|
by twic
1626 days ago
|
|
|
I know what you mean. It feels like we're missing an idea of scope for resources. If there was some kind of transaction scope or session scope or something, then a QUERY could create resources within that scope, so we could know that in the long run, it has no side effects. But that would be antithetical to the idea of statelessness perhaps. Or maybe we just need distributed garbage collection for URLs. |
|
|
Printing a URL on paper leaks it. Writing a URL down, or memorising it, also leaks it – but the computer has no way of knowing this has happened.
I don't think this is feasible.