seasonedschemer

That would be the Berkeley DeepDrive project. http://deepdrive.io/ and http://bdd.berkeley.edu/.

Thanks for pointing out, will fix that on our side!

The info in https://lyft.github.io/envoy/docs/intro/comparison.html#prox... about Proxygen not supporting HTTP/2 is not correct. Proxygen has had HTTP/2 support for a while (https://github.com/facebook/proxygen/blob/master/proxygen/li...).

Disclaimer: I work on Proxygen at FB.

Not sure if the talk covered it, but the core Proxygen framework is opensource: https://github.com/facebook/proxygen

Hey, I'm a Software Engineer on Proxygen as well. Proxygen heavily relies on folly's buffer management abstractions such as IOBuf (https://github.com/facebook/folly/blob/master/folly/io/IOBuf...) and Cursor (https://github.com/facebook/folly/blob/master/folly/io/Curso...). Protocol parsing implementation uses folly::io::Cursor to safely read byte sequences across non-contiguous buffers. Errors during parsing are wrapped up in Result types (https://github.com/facebook/proxygen/blob/master/proxygen/li...) which take an inspiration from Rust. Such constructs simplify our implementation to a reasonable extent and are still low-level enough to extract performance.

We already do support SPDY/3 and SPDY/3.1, and we're working on HTTP/2 currently.