Hi!
> In general you should not used the no arg version of dispatch(), it has been deprecated as it is not thread safe.
I understand but I have a specific need. So I'm wondering if there are better alternatives.
> If you want to just dispatch some work to a worker using the version
that takes a runnable sounds like exactly what you are after, as it will
run the runnable in a worker thread.
In fact I want/need a bit more complex thing.
I'm running undertow under Scala within ZIO. Essentially ZIO is a powerful asynchronous framework and it has a lot of async primitives.
So, I wish to efficiently integrate ZIO with undertow. From all I can understand at the moment I have only one option to do it - let undertow block in it's thread pool until my call finishes.
But I want it not to block and just provide me a callback which I may invoke once my logic finishes. And/or a way to return a promise/future/IOFuture back to undertow.
In ideal world I would like to wrap undertow within my runtime so it doesn't manage it's own threadpools (like I can do with http4s) but I guess it's not possible because all the code is monomorphic (and it's java code).
From what I can see there is no way to provide an async request handler at the moment. Maybe I miss something? Or maybe it's possible to add it?