22 ms·

And implementing TCP at Layer 7 isn't?

by jimktrains2 12y ago

jokoon 12y ago
what do you mean ?
- jimktrains2 12y ago
  HTTP2 implements stream multiplexing and flow control inside itself, instead of relying on the underlying networking protocol.
  - jokoon 12y ago
    why is that so bad ? I mean multiplexing, why not, flow control is more the job of TCP, that I agree. But if the goal is network performance and relieving stress on servers and routers and wireless internet phone equipments, I don't think it's such a bad idea. If CPUs are faster and have more cores, it might be good to let CPU do more. What I was saying is that the current problems this link is talking about, that http would try to solve, those problems are quite gore.
    - jimktrains2 12y ago
      To me the issue with multiplexing is that it's multiplexing "streams", not simply sending multiple files. (There is complete support for MIME multipart in browsers already, but if that were fixed it could be useful for "pushing" content from the server). > What I was saying is that the current problems this link is talking about, that http would try to solve, those problems are quite gore. I just don't think that HTTP2 (that name still kills me as this protocol is as much HTTP as clean coal is clean) really makes for a cleaner protocol. I think that it's being sold as HTTP is what really bothers me to the core -- it's not a replacement for HTTP; it's a Layer 4 protocol implemented at Layer 7. That's fine, I guess, but I don't think that it's inherently "simpler" than a Request-Response, text-based protocol (which, admittedly has been used to kludge a lot of things). Also, I was hoping HTTP would have solved actual issues, and not just those faced by heavy-weight websites. Issues such as: * Better authentication * More secure caching * Better methods to find alternate downloads locations * Keeping the protocol simple * Making each request contain less information about the sender * Improved Metadata (I get into those a little more here: https://github.com/jimktrains/http_ng https://github.com/jimktrains/http_ng)

And implementing TCP at Layer 7 isn't?

jokoon 12y ago

what do you mean ?

jimktrains2 12y ago
HTTP2 implements stream multiplexing and flow control inside itself, instead of relying on the underlying networking protocol.
- jokoon 12y ago
  why is that so bad ? I mean multiplexing, why not, flow control is more the job of TCP, that I agree. But if the goal is network performance and relieving stress on servers and routers and wireless internet phone equipments, I don't think it's such a bad idea. If CPUs are faster and have more cores, it might be good to let CPU do more. What I was saying is that the current problems this link is talking about, that http would try to solve, those problems are quite gore.
  - jimktrains2 12y ago
    To me the issue with multiplexing is that it's multiplexing "streams", not simply sending multiple files. (There is complete support for MIME multipart in browsers already, but if that were fixed it could be useful for "pushing" content from the server). > What I was saying is that the current problems this link is talking about, that http would try to solve, those problems are quite gore. I just don't think that HTTP2 (that name still kills me as this protocol is as much HTTP as clean coal is clean) really makes for a cleaner protocol. I think that it's being sold as HTTP is what really bothers me to the core -- it's not a replacement for HTTP; it's a Layer 4 protocol implemented at Layer 7. That's fine, I guess, but I don't think that it's inherently "simpler" than a Request-Response, text-based protocol (which, admittedly has been used to kludge a lot of things). Also, I was hoping HTTP would have solved actual issues, and not just those faced by heavy-weight websites. Issues such as: * Better authentication * More secure caching * Better methods to find alternate downloads locations * Keeping the protocol simple * Making each request contain less information about the sender * Improved Metadata (I get into those a little more here: https://github.com/jimktrains/http_ng https://github.com/jimktrains/http_ng)