Java virtual machine maintains a system-wide default group that is constructed automatically. Asynchronous channels that do not specify a group at construction time are bound to the default group. The default group has an associated thread pool that creates new threads as needed.
So, AsynchronousChannels that are created without giving them explicitly a group, are working on a different thread pool than the rest of the ZIO application. So my question is this:
Is that a problem (I guess not) and can we do better in our "opinionated" module?
The use of AsynchronousChannelGroup from the ZIO perspective is a little confusing (to me at least). As per JDK documentation:
AsynchronousChannelGroup
So, AsynchronousChannels that are created without giving them explicitly a group, are working on a different thread pool than the rest of the ZIO application. So my question is this: Is that a problem (I guess not) and can we do better in our "opinionated" module?