On 10/06/2015 03:12 PM, George Neuner wrote: > My (maybe wrong) understanding is that the response/* functions only > package the response data for the send/* functions to transmit.
They construct a `response` struct which includes an `output` procedure which, given a port, is to write the response body to it. So one might catch the exceptions in that procedure. The /xexpr and /full variations have a precomputed blob to send, ready in advance of the procedure being called, so the closure they build could swallow TCP exceptions; the more general routines take an `output` procedure directly. > However the send/* functions terminate the handler thread (possibly > with a saved continuation), so we're back to "where does the error > handler need to be?" I think those functions end up passing the results of the response/* functions out past the servlet-prompt; the `response-output` procedure is called as usual to generate the response body. Tony -- 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. For more options, visit https://groups.google.com/d/optout.
