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: });
  ----
  
  STOMP supports heartbeats. To use this feature simply configure the
  `WebSocketStompClient` with a `TaskScheduler` and if desired customize the
  default heartbeat intervals (10, 10 seconds respectively by default) for
  write inactivity which causes a heartbeat to be sent and for read
  inactivity which closes the connection.
  
  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
  
negative.code: }
  ----
  
  Once the session is established any payload can be sent and that will be
  serialized with the configured `MessageConverter`:
   
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  