reactive-streams

Currently the reference guide #content div has max-width: 62.5em set.
This is a bit on the low end for large screens in landscape mode, and could instead be set to eg. 60%.
Beyond that the rendering is starting to feel too large for paragraphs, but at 60% most large codeblocks read far better.

For phones, detecting portrait orientation and setting the max-width to 100% would also be a

reactor-pool supports metrics beyond those which reactor-netty understands: #getMaxAllocatedSize() and #getMaxPendingAcquireSize(). It would be great if these could be made available to [reactor-netty's ConnectionPoolMetrics](https://github.com/reactor/reactor-netty/blob/main/reactor-netty-co

BufferInputStream does not implement mark/reset methods of the InputStream, while we can. We should implement it to make it close to ByteArrayInputStream and ByteBufInputStream (from netty) behavior.

Problem or use case

The client is currently only logging errors and warnings. For debugging purposes and during application development, it would be very useful to also have logs detailing the message flow.

Preferred solution or suggestions

TRACE level logging for incoming and outgoing MQTT control packet types, e.g., PUBLISH, SUBSCRIBE, PUBACK, SUBACK.

We make sure in the CI configuration to build with jdk8, but it would be safer to specify this in the build (javacOptions/scalacOptions) explicitly.