anchor.diff:  the option to expose RSocket over WebSocket in a WebFlux server. There is also client
   support and auto-configuration for an `RSocketRequester.Builder` and `RSocketStrategies`.
   See the
  -https://docs.spring.io/spring-boot/docs/2.2.0.BUILD-SNAPSHOT/reference/htmlsingle/#boot-features-rsocket[RSocket section]
  +https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#boot-features-rsocket[RSocket section]
   in the Spring Boot reference for more details.
   
   Spring Security 5.2 provides RSocket support.
  
positive.code: ----
  	String securityToken = ... ;
  	ViewBox box = ... ;
  
  	Flux<AirportLocation> locations =
  		requester.route("locate.radars.within")
  			.metadata(securityToken, "message/x.rsocket.authentication.bearer.v0")
  			.data(viewBox)
  			.retrieveFlux(AirportLocation.class);
  
  
negative.code: higher level, independent concern.
  
  The main contract
  {gh-rsocket-java}/blob/master/rsocket-core/src/main/java/io/rsocket/RSocket.java[io.rsocket.RSocket]
  models the four request interaction types with `Mono` representing a promise for a
  single message, `Flux` a stream of messages, and `io.rsocket.Payload` the actual
  message with access to data and metadata as byte buffers. The `RSocket` contract is used
  