I did some hacking on the HttpCore NIO lately and added some more
features to the default I/O reactor. Now one can use the same I/O
reactor to listen on multiple ports for incoming connections and
simultaneously initiate opening of an arbitrary number of non-blocking
Here is a code sample that demonstrates the use of the new API on the
Execution of HTTP requests still requires a worker thread per
connection. This limitation I intend to tackle next. The plan is to
provide an HTTP protocol layer based on the existing HttpCore API that
can handle an arbitrary number of connections with just a handful of
threads. There are several possible implementation strategies to choose
from. If anyone is interested in discussing the options before I get
down to hacking please let me know.
Please do take a look at the new API and let me know what you think. Any
feedback, comments, critique will be hugely appreciated.