Announcement

Collapse
No announcement yet.

Firefox Begins Rolling Out QUIC + HTTP/3 Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by Azrael5 View Post
    I mean that in both cases you mention, the browser opens just https pages. So I don't understand the relevance of http/3 protocol. Is this protocol safe such as https, or is it just an evolution of http deprecated protocol?
    For the benefit of others who may not have googled either, HTTP/3 is similar to HTTP/2 (which introduced compact/efficient to parse binary headers, a type of server push, and some other things) but instead of being based on TCP, it is based on QUIC, which is a transport protocol based on UDP (rather than trying to introduce one at the level of UDP or TCP, which is basically impossible at this point). Benefits of QUIC include streams that do not block eachother (solves a problem with HTTP/2), connections that can be maintained across networks (so if you roam to LTE from WiFi, or vice versa, your QUIC connection can remain open), and faster connections (one round trip for initial connections, zero round trips for followups, vs. a minimum of three round trips for a TLS TCP connection).

    Comment


    • #32
      Originally posted by microcode View Post

      For the benefit of others who may not have googled either, HTTP/3 is similar to HTTP/2 (which introduced compact/efficient to parse binary headers, a type of server push, and some other things) but instead of being based on TCP, it is based on QUIC, which is a transport protocol based on UDP (rather than trying to introduce one at the level of UDP or TCP, which is basically impossible at this point). Benefits of QUIC include streams that do not block eachother (solves a problem with HTTP/2), connections that can be maintained across networks (so if you roam to LTE from WiFi, or vice versa, your QUIC connection can remain open), and faster connections (one round trip for initial connections, zero round trips for followups, vs. a minimum of three round trips for a TLS TCP connection).
      Thanks. I red about QUIC long time ago when my attention was attracted by this feature in a based chrome browser enabling it in the flag page of the browser. Yes, QUIC makes faster some operations. Now, I remember about it thanks to your explanation. From then I didn't know what was happened to this protocol. I remember it as an option to apply to improve web browsing. And alongside it there was http/2... but less performant. Long time has passed.
      Last edited by Azrael5; 19 April 2021, 09:31 AM.

      Comment


      • #33
        Originally posted by microcode View Post

        Mozilla foundation has a lot of money, and more of it than ever goes to top level executives. While they were laying off engineers throughout last year, they were giving themselves raises.
        And there was the rather absurd situation a few months back where the two leading mozilla blog posts were about browser privacy -- one from firefox engineering and one from the CEO. The post by engineering spelled out advances in browser privacy features and the post by the CEO lamented the dangers of internet privacy.

        Comment


        • #34
          Originally posted by klapaucius View Post
          well I must be slightly on the Asperger's spectrum then, because i didn't get it.
          in this particular example, the post had warning signs that it was trolling: multiple exclamation points, all caps "wtf", absolutism with "by definition" as if it's a universal fact, nothing other than Rust making sense (ignoring similar languages like Go, though it does relate to mozilla being the start of rust), calling c++ "shriveling" (regardless of a decline, it might take decades to become shriveling), just the entire outrage of that whole post on a relatively mundane topic, almost any rust or even any code topic could/should end up with a meme reply about (re)writing in rust

          Comment

          Working...
          X