title: Connecting to WebAPI from different clients
body: <p>I've come across a number of posts describing the Web API pipeline.  In particular, I saw how you are able to inject some code into the MessageHandlers by inheriting from DelegateHandlers.  The exciting part of this feature is you can wrap your Authentication plumbing in the handler.</p>
  
  <p>Here is an example:</p>
  
  <p><a href="http://sixgun.wordpress.com/2012/02/29/asp-net-web-api-basic-authentication/" rel="nofollow">http://sixgun.wordpress.com/2012/02/29/asp-net-web-api-basic-authentication/</a></p>
  
  <p>In most of the examples, I have only seen C# clients using the HttpClient class to call into WEB Api.</p>
  
  <p>How would other clients connect to my Web Api service if I implement a custom handler to manage my Authentication?</p>
  
  <p>In others words, how would an Android, iOS, or AJAX application connect to my service?  Do each of these clients have to implement 'their' version of HttpClient so they can perform an SendAsync?</p>
  
  <p>Thanks.</p>
  
  <p>Steve</p>