Add Simpler Data Methods

“I feel like Flux<ByteBuffer> is an advanced use case, in the already-advanced async world. I wonder if there should be additional API here that takes either ByteBuffer directly, or simply an OutputStream similar to the sync case.”

Look into adding OutputStream methods that correspond to the Flux<ByteBuffer> methods in the async clients. Update the sync methods to pass through their OutputStream to the async method.

[conniey]

In my opinion, the download() return value (ie. Mono<Flux<ByteBuffer>>) isn’t intuitive. When you tell the BlobAsyncClient you want to download an item, I expect it to return a stream of bytes for me to do whatever with.

Instead it returns a Mono that could either complete with an error, nothing, or a stream of bytes that I then have to unwrap to consume. The same set of scenarios can be accomplished with: Flux<ByteBuffer>.

Working with this API during the storage scavenger hunt was cumbersome because I had to use a .flatMap to toss out the Mono before being able to consume the byte buffer.

With Mono<Flux<ByteBuffer>>

private static Mono<Void> handleDownload(Mono<Flux<ByteBuffer>> contents) {
    return contents
            .flatMap(buffer -> buffer.reduce(ByteBuffer.allocate(0), App::concat))
            .map(concatenate -> {
                final CharBuffer decode = StandardCharsets.UTF_8.decode(concatenate);
                System.out.printf("Item: %s%n%n", decode);
                return decode;
            }).then();
}

With Flux<ByteBuffer>

private static Mono<Void> handleDownload(Flux<ByteBuffer> contents) {
    return contents
            .reduce(ByteBuffer.allocate(0), App::concat)
            .map(concatenate -> {
                final CharBuffer decode = StandardCharsets.UTF_8.decode(concatenate);
                System.out.printf("Item: %s%n%n", decode);
                return decode;
            }).then();
}

[vhvb1989]

Closing this for now.