anchor.diff:  session.send("/topic/foo", "payload");
   ----
   
  -The subscribe methods take a `StompFrameHandler` for messages on the subscription
  -and return a `Subscription` handle for unsubscribing. For each received message,
  -the handler must help to select the target type and then handle the
  -deserialized payload:
  +You can also subscribe to destinations. The `subscribe` methods require a handler
  +for messages on the subscription and return a `Subscription` handle that can be
  +used to unsubscribe. For each received message the handler can specify the target
  +Object type the payload should be deserialized to:
    
   [source,java,indent=0]
   [subs="verbatim,quotes"]
  
positive.code: }
  ----
  
  Send any Object as the payload and it will be serialized with a `MessageConverter`:
   
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  
negative.code: });
  ----
  
  To enable STOMP heartbeat configure `WebSocketStompClient` with a `TaskScheduler`
  and optionally customize the heartbeat intervals, 10 seconds for write inactivity
  which causes a heartbeat to be sent and 10 seconds for read inactivity which
  closes the connection.
  
  [NOTE]
  ====
  When using `WebSocketStompClient` for performance tests to simulate thousands
  of clients from the same machine consider turning off heartbeats since each
  connection schedules its own heartbeat tasks and that's not optimized for a
  a large number of clients running on the same machine.
  ====
  
  
  The STOMP protocol also supports receipts where the client must add a "receipt"
  header to which the server responds with a RECEIPT frame after the send or
  