anchor.diff:  	}
   ----
   
  -A custom `ChannelInterceptor` can extend the empty method base class
  -`ChannelInterceptorAdapter` and use `StompHeaderAccessor` or `SimpMessageHeaderAccessor`
  +A custom `ChannelInterceptor` can use `StompHeaderAccessor` or `SimpMessageHeaderAccessor`
   to access information about the message.
   
   [source,java,indent=0]
  
positive.code: implement their own reconnect logic.
  ====
  
  Furthermore, an application can directly intercept every incoming and outgoing message by
  registering a `ChannelInterceptor` on the respective message channel. For example
  to intercept inbound messages:
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  
negative.code: 		}
  	}
  ----
  
  Note that just like with the `SesionDisconnectEvent` above, a DISCONNECT message
  may have been sent from the client, or it may also be automatically generated when
  the WebSocket session is closed. In some cases an interceptor may intercept this
  message more than once per session. Components should be idempotent with regard to
  multiple disconnect events.
  
  
  
  