News for hackers. Stuff that matters.

A comment on The Future (and the Past) of the Web Is Server Side Rendering. Parent comment

Re:The Future (and the Past) of the Web Is Server Side Rende... by throwawaymaths on Saturday February 04, 2023 @01:20AM (#34652075)
By chuck away I mean all those processor cycles to perform cryptographic verification... And then throw away the result because you have to do it on the next connect anyways

And I have written a library that does the full SSL handshake/upgrade cycle off of tcp sockets, and managed my own private CA, so I'm not a total idiot.

[ Parent | on HN ]
Re:The Future (and the Past) of the Web Is Server Side Rende... by dan1234 on Saturday February 04, 2023 @02:54AM (#34652599)
Isn’t that mitigated with TLS session resumption and TLS 1.3’s 0-RTT?
[ Parent | on HN ]
Re:The Future (and the Past) of the Web Is Server Side Rende... by kaba0 on Saturday February 04, 2023 @03:08AM (#34652673)
How is that different than all the other CSR SPAs that do a REST call on every button press as well? They do almost the same amount of work, and will also “throw away” the results.
[ Parent | on HN ]
Re:The Future (and the Past) of the Web Is Server Side Rende... by throwawaymaths on Saturday February 04, 2023 @07:01AM (#34653817)
It's not, but there are server side options (topic of op) where it's a websocket. I believe HTMx supports ws too, but gp was only talking about RESTful round-trips
[ Parent | on HN ]