NIO has significant impact on HTTP Servers not on stand alone single instance clients.

The only time you'd use a NIO client, is on a server - for example, when building a caching proxy server.

The expected benefits are higher throughput of the proxy (lower CPU/RAM consumption allows multiple clients to operate in parallel).

Individual downloads being faster was never expected to be a benefit

> NIO has significant impact on HTTP Servers not on stand alone single instance clients.

This is true for the asynchronous network IO parts of NIO, but definitely not all of it. It also enables memory mapping and DMA, two things that can have significant impact on stand alone software.

I'd start a business that would have offices in the top 20 major commercial cities in the world and would trade physical commodities taking advantages of the price differences between these locations. My business would use telephone or telegraph.

The presence of the internet and ensuing information exchange reduces these price differences to make such a business nonviable.

My company runs a contextual advertising network that could be plugged in with your widget on your publishers pages.

(Can also do non-obtrusive text links which should be more acceptable to your publisher base than banners)

We could really help with the entire monetize using advertising strategy but our service is currently not public.

Contact me offline for details (see profile). (Sorry can't reveal corporate info at this point, apropos of not being public)