On Sat, Jul 03, 2021 at 04:20:12PM -0700, Amit Saha wrote:
When writing HTTP servers in Go, a panic() in a request handler doesn't abort the entire process as it has a recovery mechanism setup (https://golang.org/src/net/http/server.go?s=99233:99288#L81). With gRPC it seems that's not the case - so i assume there is a good reason we don't have a recover() in the goroutine executing the service handler. I was curious if anyone knew what the reason was?
The described behaviour in the net/http package is widely considered (including by its original author) to be a misfeature. Therefore, it only makes sense to not repeat the same mistake in gRPC.
-- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/YOEBbg1XAVnktEsF%40horsthansen.slrz.net.
