4 ms·
But before you use RPC, try rendering your markup on the server. That, too, reduces a lot of complexity.
by mark_and_sweep 4y ago
But before you use RPC, try rendering your markup on the server. That, too, reduces a lot of complexity.
- deleted 4y ago[deleted]
- samarthr1 4y agoAt cost of reducing cache ability though no? It is cheaper for me to put my react app in front of a cdn, split out my app into an api and front end than for me to have my site be entirely uncacheable. I can also cache certain endpoints behind the cdn that are mostly invariant for users. And, the network egress of json is much lesser than the egress of markup.
- jddil 4y agoWhat? Server rendered content is infinitely more cacheable, maybe I'm not understanding what you're saying. In the boring old days we just did it all on the server and used the semantics of HTTP to handle caching ... it worked great.
- mark_and_sweep 4y agoIf you are truly concerned about network costs, I'd recommend rendering an XML model on the server and using a cached extensible stylesheet (XSLT) to render your HTML on the fly, on the client.
- runald 4y agoand let all the non-browser clients parse html?
- mark_and_sweep 4y agoNo, that's the RPC part.