On 10/6/2015 9:58 AM, Jay McCarthy wrote:
I'm not sure if this answers the question...
These errors are coming from the Web server response-outputing code
failing when the other side closed the connection early. The exception
would not be returned to your code, because your code is a function
from "request -> response" rather than a "request -> void" function
that ends with a call to "output this response". So, the exception is
thrown on the Web server's side and will just get caught be the
connection thread's handler, which just prints it out and cleans up
for the connection. The only way you could grab this would be to make
a different dispatcher that called your servlet and then ran its own
"output this response" code from a context you controlled.
That's about what I figured.
In any case, what would you expect to do with such an exception? The
connection is gone and you can't do anything about it?
TCP reset is analogous to other communication breakdowns in that it
means at least some data you sent was not delivered. The only real
difference is that it is the result of a deliberate act by the client
rather than caused by a crash or myriad possible network problems.
Given the request-response nature of HTTP, I can't think of a realistic
use for the exception. If "push" HTTP had caught on, the situation
might have been different.
George
--
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.
