anchor.diff:  
   		@Override
   		public void registerStompEndpoints(StompEndpointRegistry registry) {
  -			registry.addEndpoint("/portfolio").withSockJS();
  +			registry.addEndpoint("/portfolio").withSockJS();  // <1>
   		}
   
   		@Override
   		public void configureMessageBroker(MessageBrokerRegistry config) {
  -			config.setApplicationDestinationPrefixes("/app");
  -			config.enableSimpleBroker("/topic", "/queue");
  -		}
  -	}
  -----
  -
  -and in XML:
  +			config.setApplicationDestinationPrefixes("/app"); // <2>
  +			config.enableSimpleBroker("/topic", "/queue"); // <3>
  +		}
  +	}
  +----
  +
  +<1> `"/portfolio"` is the HTTP URL for the endpoint to which a WebSocket (or SockJS)
  +client will need to connect to for the WebSocket handshake.
  +<2> STOMP messages whose destination header begins with `"/app"` are routed to
  +`@MessageMapping` methods in `@Controller` classes.
  +<3> Use the built-in, message broker for subscriptions and broadcasting;
  +Route messages whose destination header begins with "/topic" or "/queue" to the broker.
  +
  +The same configuration in XML:
   
   [source,xml,indent=0]
   [subs="verbatim,quotes,attributes"]
  
positive.code: 
  ----
  
  The following explains the message flow for the above example:
  
  * WebSocket clients connect to the WebSocket endpoint at "/portfolio".
  * Subscriptions to "/topic/greeting" pass through the "clientInboundChannel"
  and are forwarded to the broker.
  * Greetings sent to "/app/greeting" pass through the "clientInboundChannel"
  and are forwarded to the `GreetingController`. The controller adds the current
  time, and the return value is passed through the "brokerChannel" as a message
  to "/topic/greeting" (destination is selected based on a convention but can be
  overridden via `@SendTo`).
  * The broker in turn broadcasts messages to subscribers, and they pass through
  the `"clientOutboundChannel"`.
  
  The next section provides more details on annotated methods including the
  kinds of arguments and return values supported.
  
negative.code: 
  [NOTE]
  ====
  For the built-in, simple broker the "/topic" and "/queue" prefixes do not have any special
  meaning. They're merely a convention to differentiate between pub-sub vs point-to-point
  messaging (i.e. many subscribers vs one consumer). When using an external broker, please
  check the STOMP page of the broker to understand what kind of STOMP destinations and
  prefixes it supports.
  ====
  
  
  