3 ms·
It's http2-based, completely different implementation compared to http1.
by theogravity 3y ago
It's http2-based, completely different implementation compared to http1.
- jauntywundrkind 3y agoIt's difficult to stress how little I care about using a decade old+ version of http versus a 2 decade old+ version. This only further exacerbates my feeling that there's not actually a significant & real complaint against grpc or it's complexity, if we're arguing one of the most well established rfc's is the issue. That's not a grpc issue at all. Does grpc have an issue, or is this just general vague pissy anti-modern bellyaching in general? Cause it started insubstantial as heck to start from & if this is the first go to argument, my gods man, zero tolerance for this whiner shit. This is the times. Grpc is not at fault here for using vaguely modern competent protocols. What shit.
- theogravity 3y agoI agree. gRPC shouldn't be at fault. From my understanding, it's browsers (Javascript, rather) that are at fault as they don't implement specific http2 features that gRPC requires when it comes to web, which is why an envoy proxy is required (but also comes with limitations). As a result, when it comes to web comm, gRPC isn't given a chance. https://yuku.takahashi.coffee/blog/2019/01/grpc-proxy-for-grpc-web https://yuku.takahashi.coffee/blog/2019/01/grpc-proxy-for-gr...