Norman Gray writes:
> But what happens in this case (the my-app/error case in my example) is > that the (server) program keeps going but the client stalls. The > unexpected error in the response-output procedure is caught, and (as > far as I can see) handled by killing the producer thread _without_ > closing the connection. To be clear, I think that the handler should > do both. The handler you pointed to in your other email is intended to catch network errors and abrupt hangups from the client, but will not catch exceptions raised by the response's output function. For that, there needs to be an exception handler in the chunker thread. I've opened a PR to add such a handler here: https://github.com/racket/web-server/pull/93 -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/m2mu5vu1v5.fsf%40192.168.0.142.
