|
|
|
|
|
|
by c8d3f7b49897918
3094 days ago
|
|
|
> The Turbolinks/Intercooler approaches seem to be managing state with the DOM, I won't speak for turbolinks, but with intercooler the idea is to return to a stateless architecture, the second aspect of the REST-ful architecture[1]. State, as such, is stored on the server, not on the client. It has scaled quite well in my applications: browsers are very fast at swapping new HTML into a page. The downsides can be additional chattiness with a server and a lack of interactivity if you are building a fancy (or fancy part of an) application, such as a game. In those cases, intercooler is not a good choice. [1] - https://en.wikipedia.org/wiki/Representational_state_transfe... |
|
|