Tell us what you like and what you'd want to see. 💁

[markjschreiber]

We'd love to hear more about how you use aws-java-nio-spi-for-s3, what you use it for, what you like about it and what changes or new features you would like to see.

Feedback is always welcome and helps us improve the package.

[nikolaydnedelkov]

@markjschreiber How exactly S3SeekableByteChannel can be used ? It is not accessible when the library is included as a maven dependency? SeekableByteChannel is not public, but package-private/default class.

[markjschreiber]

You don't use it directly. As a service provider, having the JAR on your classpath means that Java will recognize URIs beginning with s3:// as being handled by this library and delegate operations to the classes of this library. In the example in https://github.com/awslabs/aws-java-nio-spi-for-s3/blob/main/src/examples/java/software/amazon/nio/spi/examples/FileChannelDemo.java you are using completely vanilla java NIO code, but if the URI is from S3 then the channel is an instance of an S3 specific byte channel.

The advantage of the approach of using standard NIO classes and letting the VM figure out which provider to use is that the same code can work with your local filesystem and with any other filesystem SPI you have.

If you specifically need to tell the compiler you are working with an S3SeekableByteChannel then you could cast it. Probably after checking with instanceof first.

Do you have a specific use case where you would want a public constructor?