Is this source sound for a "flow" based on Http().superPool(...) :
BlockingQueue<HttpRequest> queue = new LinkedBlockingQueue<>();
Source< HttpRequest, ?> source = Source.fromIterator(() ->
new Iterator<HttpRequest>() {
public boolean hasNext() {return true;}
public HttpRequest next() {
try {
return queue.take();
} catch (InterruptedException e) {}
return null;
}
});
So many clients will be adding async many HttpRequests to the single queue
and the flow (based on Http().superPool(...)) should then process theses
requests.
I do think that using a concurrent LinkedBlockingQueue does scale. But is
there an alternative?
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.