anchor.diff:  
    1. The client sends a Request only and we can
   still use xref:components::http-component.adoc[HTTP] despite http being
  -Request Reply by nature. +
  +Request Reply by nature.
    2. Camel invokes an external xref:components::mina-component.adoc[TCP] service using
   synchronous Request Reply. The client
  -application is still waiting. +
  +application is still waiting.
    3. The message is processed completely and the control is returned to
   the client.
   
  -So why do you want to use synchronous xref:event-message.adoc[Request Only]? 
  +So why do you want to use synchronous xref:event-message.adoc[Request Only]?
   Well if you want to know whether the message was processed
   successfully or not before continuing. With synchronous it allows you to
   wait while the message is being processed. In case the processing was
  
positive.code: 
   1. The client sends a sync Request Reply
  message over xref:components::http-component.adoc[HTTP] to Camel. The client application will
  wait for the response that Camel routes and processes. +
   2. The message invokes an external xref:components::mina-component.adoc[TCP] service using
  synchronous Request Reply. The client
  application still waits for the response. +
   3. The response is sent back to the client.
  
  [[Async-AsynchronousRequestReply]]
  
negative.code: information on this page applies for Camel 2.0 and later.
  
  The Async API in Camel is primarily divided in two
  areas:
  
   1. Initiating an Async messaging from the client
   2. Turning a route into Async using the *threads* DSL
  
  Before we look at these two areas we start with a bit of background
  information and look at the concept from a higher level using
  