Giovanni Barillari

> Basically all these options in here: https://ssl-config.mozilla.org/#server=nginx&version=1.26.0&config=intermediate&openssl=1.1.1w&guideline=5.7 > > To name a few I don't see an equivalent: ssl_stapling, ssl_ciphers, ssl_prefer_server_ciphers, ssl_protocols, ssl_dhparam, ssl_session_cache, ssl_session_timeout. Fair enough, I encourage...

> I suspect you have compared nginx+uwsgi (a badly configured uwsgi at that) against a naked granian (no proxy) with the most efficient protocols available (http2/rsgi). You have to put...

> it would be nice to have socket activation support - so listening on a file descriptor passed from the process manager (eg. systemd). > > it would be fantastic...

> so are you saying we are forced to migrate all our existing web projects to Granian-supported interfaces, in order to use Granian? that would not spark joy :( while...

Ideal implementation notes (as of 2.3 code): - an additional `accept_loop uds` macro which implement `tokio::net::UnixListener` in place of `TcpListener` - consequential `gen_accept` macros - consequential `serve_mtr_uds`, `serve_str_uds`, `serve_fut_uds` macros...

> One reason to support Unix domain sockets that I don't see addressed above is security. When an app is deployed listening on a Unix domain socket (with e.g. nginx...

> I don't think it is possible to do this with TCP sockets, even with Docker/containers, unless you start playing games with iptables rules and the `uid` matcher. You can...

> Unfortunately it returns a `tokio::net::unix::SocketAddr` which is a different type from the `core::net::SocketAddr` returned by `TcpListener`. Ah, I see. Then we need an `enum` and pass that to the...

This is now done and will be released in 2.5. For anyone interested into this and willing to build granian from source at the current master: I'd appreciate you to...

> The current implementation looks like it's either or. It is, and I'm afraid there's not an easy path to change this. The listen loop happens on a single listener,...