On 10/06/2015 12:43 AM, George Neuner wrote: > I don't know where to put an error handler to deal with reset conditions > at the end of a request. Maybe Jay has an idea?
It feels like exceptions are something that response/full, response/xexpr and similar procedures could deal with, since they have a "fire and forget" flavour to them. Raw response objects wouldn't trap the exceptions, and so neither would response/output. The rule of thumb I have in mind is: if you're dealing with the response port at all, catching network exceptions is your responsibility. If the port is entirely hidden away from you, exception handlers would Do The Right Thing For You. Perhaps something like that might help the situation? 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.
