When a client disconnects, I see that onClose is not being fired. The only
way this seems to be firing if client sents a close frame.
Is there any way to detect disconnection and immediately close all the
Robin Anil | Software Engineer
is there any documentation on what interfaces are thread-safe and what isn't?
As I understand it (please correct me if I'm wrong):
1. HttpServerExchange is not thread-safe (dispatch should be used to serialize access to it);
2. WebSocketChannel is thread-safe, so is it OK to call suspendReceives/resumeReceives from different threads.
What about other interfaces?
Could you give me a hint if there is a way to write asynchronous handlers?
So, I have my own asynchronous runtime (namely ZIO) and I wish undertow's
worker thread to do something while it's waiting for request completion
after a `dispatch` in my handler.
Is there an API allowing me to return a Future or undertow's IOFuture so I
may write an adaptor for my primitives?..
>From what I can see there is that zero-arg `.dispatch()` method which just
changes internal flag. So, from what I can understand I may just set that
flag and then complete my request totally asynchronously. Though that
method is marked deprecated without an alternative - other versions also
wait for a `Runnable`.