Github from Haiku browsers

Confusion, again.

HTTP is not HTML.

The HTML, CSS, javascript will still be plain text when transported with HTTP2. HTTP2 is just a protocol, like IP, or TCP. Would you suggest that TCP should be plain text now?

The simple HTTP from the early days simply isn’t enough for many modern features and ends up being a pain to use. Over the years, piles of hacks were added on top of it to work around the limitations: AJAX, then streamed AJAX, then WebSockets, for example.

The HTTP2 protocol will allow to do these things in a cleaner way. It is a low level protocol, providing multiple streams of data over a single TCP connection. The goal is not to tie down anything, it’s just to reduce load on servers (single TCP connection per client) and speed things up.

As for the DRM aspects, I think DRM is a bad idea and avoid it when I can. However, DRM is happening anyway, and the best the W3C can do is make sure it is at least implemented with documented protocols and technologies, and if possible, free of patents. At least this would allow Haiku to implement it for people who want to use DRM crippled media, for example. If we have DRM+patents+undocumented protocols, then there is nothing we can do.

Thanks for straightening things out! Been listening to too many scare stories I guess…:slight_smile:

1 Like