anchor.diff:  the WebSocket sink does not. It may happen that a failure to receive a message is not reported,
   e.g. if the remote side closes the WebSocket connection in a crucial moment.
   
  +The `quarkus-websocket` connector is configured with the following properties:
  +
  +[source,properties]
  +----
  +# OUTGOING
  +
  +# The target URL
  +mp.messaging.outgoing.<channelName>.url=ws://localhost:8234/
  +
  +# Message serializer, optional, implementation of `io.quarkus.reactivemessaging.http.runtime.serializers.Serializer`
  +mp.messaging.outgoing.<channelName>.serializer=com.example.MySerializer
  +
  +# The number of retries to make for sending a message to a remote websocket endpoint.
  +# A value greater than 0 is advised. Otherwise, a web socket timeout can result in a dropped message
  +# The default value is 1
  +mp.messaging.outgoing.<channelName>.maxRetries=1
  +
  +# Configures the random factor when using back-off with maxAttempts > 1, 0.5 by default
  +mp.messaging.outgoing.<channelName>.jitter=0.7
  +
  +# Configures a back-off delay between attempts to send a request.
  +# A random factor (jitter) is applied to increase the delay when several failures happen.
  +mp.messaging.outgoing.<channelName>.delay=2s
  +
  +
  +# INCOMING
  +
  +# The path of the endpoint
  +mp.messaging.incoming.<channelName>.path=/my-ws-endpoint
  +
  +# Web socket endpoint buffers messages if a consumer is not able to keep up.
  +# This setting specifies the size of the buffer. 8 by default
  +mp.messaging.incoming.<channelName>.buffer-size=3
  +----
  +
   === Reactive Messaging
   This extension utilizes MicroProfile Reactive Messaging to build data streaming applications.
   
  
positive.code: 
  Open `http://localhost:8080/index.html` in your browser.
  
  NOTE: If you started the AMQP broker with docker compose, stop it using `CTRL+C` followed by `docker-compose down`.
  
  == Running Native
  
  
negative.code: 
  == Get it running
  
  Run the application using:
  
  [source,bash]
  ----
  