anchor.diff:  *Input*
   
   The HTTPTrigger attribute on the req param tells Azure that this function should be exposed as a HTTP endpoint, the HttpRequest is available in the req object, allowing you full access to headers, form data, etc.  
  +r
  +image:azure_functions/part1/invoke_http_function.png[]
   
   *Output*
   
  
positive.code: Disclaimer, all these examples are trivial and contrived, none even resemble a prototype. 
  
  ====== Trigger Movie Process 
  
  .
  image:azure_functions/part1/seq1.png[]
  
  
negative.code: 
  The method returns a Http response to sattisfy the http request. 
  
  image:azure_functions/part1/trigger_movie_process_log.png[]
  
  ==== Download movie data 
  
  image:azure_functions/part1/seq2.png[]
  
  The second Function in the pipeline is triggered by any message in the _TriggerMovieProcessQueue_. 
  
  image:azure_functions/part1/download_movie_data_log.png[]
  
  [source, csharp]
  ----
  