31–40 of 98 posts
Hey there, I work on Proxygen at Facebook. I'm happy to answer any questions you have about the project.
How tested is the websocket support? Does facebook use this for TLS termination?
Hey there, I work on Proxygen at Facebook. I'm happy to answer any questions you have about the project.
I currently use nginx for all my projects, which for me mostly consist of (1) serving static content and (2) proxying to gunicorn. My setups are usually not overly complicated, basic redirects for stuff like www/non-www or ssl/non-ssl, installing ssl certs can be a pain sometimes, and for the most part I use a lot of default settings and have never needed to go in-depth with tweaking settings. Does somebody like me h…
If you're interested in how HTTP frameworks are designed and implemented, I'd definitely suggest checking it out though. This project is initially going to be more interesting to people integrating with HTTP quite directly.
I really like your idea of the 4-part abstraction. Still… Your library really is not "that" easy to use. I'm currently working on my own library using libuv, http-parser, nghttp2 and wslay, which is very similiar in it's use to node.js. As you might guess a echo server is therefore only about 15 lines of code, but about as performant as your framework. The downsite is that it's not as flexible due to the missing "4-p…
I really like your idea of the 4-part abstraction. Still… Your library really is not "that" easy to use. I'm currently working on my own library using libuv, http-parser, nghttp2 and wslay, which is very similiar in it's use to node.js. As you might guess a echo server is therefore only about 15 lines of code, but about as performant as your framework. The downsite is that it's not as flexible due to the missing "4-p…
I really like your idea of the 4-part abstraction. Still… Your library really is not "that" easy to use. I'm currently working on my own library using libuv, http-parser, nghttp2 and wslay, which is very similiar in it's use to node.js. As you might guess a echo server is therefore only about 15 lines of code, but about as performant as your framework. The downsite is that it's not as flexible due to the missing "4-p…
Also Facebook is a group of people so saying "your" doesn't really sound right.
"You will need at least 2 GiB of memory to compile proxygen and its dependencies." What?
I really like your idea of the 4-part abstraction. Still… Your library really is not "that" easy to use. I'm currently working on my own library using libuv, http-parser, nghttp2 and wslay, which is very similiar in it's use to node.js. As you might guess a echo server is therefore only about 15 lines of code, but about as performant as your framework. The downsite is that it's not as flexible due to the missing "4-p…
Care to show us what you've got instead of just saying how much better it is than Proxygen? Also Facebook is a group of people so saying "your" doesn't really sound right.
In no way I intended to say that my framework is better overall, but I do think it's better suited for simple things, like apps.
In fact, I think I will integrate something like their "four-part abstraction", because I really think this is a great idea.