3 ms·

Huh? How does HTMLx "chuck" away SSL (you meant TLS, right? I hope you're not using SSL) and encrypted cookies? How about you try it and see?

• devin 4y ago
  It’s fine to use SSL interchangeably with TLS IMO. It’s still called OpenSSL.
  • movedx 4y ago
    I suppose, but it's not really that big of an effort to just use the correct term for the correct version of the technology.
    • throwawaymaths 4y ago
      The certs are generally called SSL certs, not tls certs, too.
      • movedx 4y ago
        > AWS Certificate Manager - Provision and manage SSL/TLS certificates with AWS services and connected resources Both, I guess.
• throwawaymaths 4y ago
  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.
  • dan1234 4y ago
    Isn’t that mitigated with TLS session resumption and TLS 1.3’s 0-RTT?
  • kaba0 4y ago
    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.
    • throwawaymaths 4y ago
      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