I need async http, and I think it really needs to be driven by Akka's thread pool management.
Looking at this thread:
and the async-http-client and spray-can-client.
I'm in a Java centric environment, which mostly rules out spray-can, but I want akka integrated thread pool for async http calls.
Please correct me if I'm wrong, but async-http-client uses and j.u.c.ExecutorService, but Akka doesn't provide that interface, so it can't natively run j.u.c.ExecutorService jobs for other libraries. That thread above mentioned a bridge, but from what I understand, it talked about taking async-http-client's j.u.c. ExecutorService and providing it to an Akka system for use. To me I thought it would make more sense to have async-http-client use Akka's thread managed pool.
So, I can implement j.u.c.ExecutorService, and have it delegate to ActorSystem#dispatcher()#execute(); Is it really as straight forward as that?