manual
manual copied to clipboard
Documentation: Deno.listen vs. listenAndServe
I've run into numerous articles informing about the new fast and native HTTP server via the runtime Deno.{listen,serveHttp}. However, most examples that are available use the higher-level listenAndServe pulled from std. I would love to know more about differences between these two layers, i.e. what exactly is listenAndServe doing for me (and for what price/overhead) when compared to the pure-runtime approach (which honestly is not that awfully verbose).