Feature Request: access to EventLoopGroup

[mlilback]

According to documentation, an application should generally have a single EventLoopGroup. Kitura-NIO create its own group and threads, and provides no access. Performance will suffer if every library used creates its own group.

I'd like the options:

1. To create my own group, and pass it into Kitura.
2. If a group is not specified and Kitura creates one, n accessor to get that group.

[weissi]

I agree, especially option 1 sounds like a good plan to me. In async-http-client for example there’s the EventLoopGroupProvider type to do this.

[pushkarnk]

Sounds reasonable to me. We'd be deviating from the Kitura-net API, but I assume that developers who want to use NIO's types may not really consider switching over to Kitura-net.

Your thoughts @djones6 ?

[djones6]

I think that deviation from Kitura-net is okay in this instance. As long as the expectation is clear that the application is then tightly coupled to Kitura-NIO, I don't see a problem with providing additional features such as this.

[harish1992]

Hi @mlilback, PR #225 adds this feature.