An RSocketServer extending RSocket could be a runtime detected feature that allows invoking a 2-arguments Payload/Publisher RSocket handler method.

The reason for a 2-arguments is to explicitly separate the first Payload possibly carrying routing informations (rsocket/rsocket#254) or any other such as tracing, composite etc. All others interactions do not have this issues having a single Payload argument readily available for introspection where requestChannel requires the user to peek the first emitted Payload to achieve the same effect.