On 12/12/2016 01:11 AM, Alan Bateman wrote:
On 11/12/2016 22:38, David M. Lloyd wrote:
I'm not implementing SelectorProvider, I just want access to all the
possible implementations that are available in the current JDK so we
can select among them on a case-by-case basis.
Are you attempting
t
On 11/12/2016 22:38, David M. Lloyd wrote:
I'm not implementing SelectorProvider, I just want access to all the
possible implementations that are available in the current JDK so we
can select among them on a case-by-case basis.
Are you attempting
to wrap the default implementation - I ask
On 12/11/2016 05:18 AM, Alan Bateman wrote:
On 10/12/2016 15:21, David M. Lloyd wrote:
Would it be possible to have all available selector provider
implementation classes listed in a "provides java.nio.channels.spi
with ..." section of java.base's module descriptor? My use case is as
follows:
On 11/12/2016 11:44, Remi Forax wrote:
:
No, these are different implementation, they directly use classes from
sun.nio.ch and bypass the selector API.
Sure, but the SelectorProvider service interface doesn't define anything
that allows someone to choose when there are multiple implementation
- Mail original -
> De: "Alan Bateman"
> À: "David M. Lloyd" , "jigsaw-dev"
>
> Envoyé: Dimanche 11 Décembre 2016 12:18:26
> Objet: Re: Module exports for java.base: NIO stuff
> On 10/12/2016 15:21, David M. Lloyd wrote:
>
>
On 10/12/2016 15:21, David M. Lloyd wrote:
Would it be possible to have all available selector provider
implementation classes listed in a "provides java.nio.channels.spi
with ..." section of java.base's module descriptor? My use case is as
follows:
Our I/O library (XNIO) relies on the abil
Would it be possible to have all available selector provider
implementation classes listed in a "provides java.nio.channels.spi with
..." section of java.base's module descriptor? My use case is as follows:
Our I/O library (XNIO) relies on the ability to detect and use different
available sel
