Writing web applications using only the Go Standard Library

Re:Writing web applications using only the Go Standard Library by TazeTSchnitzel on Saturday December 24, 2016 @01:29PM (#13250994)

> Not handling something as basic as timeouts properly for many years suggests that nobody actually uses built-in server for anything complex standalone, but more likely behind nginx and without direct communications with a hostile world.

Sure, but from what I know, Go actually supports them now. As problems are discovered, they will be dealt with. It saves you reinventing the wheel.

You had suggested writing your own simple HTTP/1.0 implementation. HTTP/1.0 is not enough for talking to the outside world. It lacks vhosts, it lacks keepalive. You lack HTTPS support too without adding your own TLS layer. You would have to use nginx or something in front for it to be ready for the outside world. By your logic, wouldn't Go's own HTTP server be fine, then? It'd certainly be easier.

[ Parent | on HN ]

Re:Writing web applications using only the Go Standard Library by zzzcpan on Saturday December 24, 2016 @05:55PM (#13251967)

Go's own http server behind nginx would be fine, until it won't. Which was my whole point. Let's say you have to deal with streaming through the server, you will have to learn the hard way that there is no way to set timeouts there even today.

[ Parent | on HN ]