AFAICT this is the intended behavior. To me it is consistent with the usual policy: an uncaught error stops the program. If you want the program to keep running, then you have to catch the error and make other arrangements. All my servlet routes are surrounded by a top-level `with-handlers` block that catches `exn:fail?`. If I get an error, I usually a) log it to the remote system, b) send an email to myself, and c) send a status 400 response to the browser with the error string. But the web server keeps running as usual.
> On May 25, 2020, at 10:30 AM, Norman Gray <norman.g...@glasgow.ac.uk> wrote: > > This means that a further possibility is to have an exception handler within > the serialiser, and handle exceptions appropriately there (as in > my-app/handlers above). However all this means that a carefully-written > servlet _must_ have such handlers, if an inadvertent exception in the > serialiser procedure isn't to stall a client. -- 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/D9679928-BF4D-4115-8E28-5D4D6FAC48B9%40mbtype.com.
