title: Can I incorporate both SignalR and a RESTful API?
body: <p>I have a single page web app developed using ASP.NET.  I recently converted many of the web methods to be push based, using the <a href="http://signalr.net/" rel="noreferrer">SignalR</a> library.  This really sped up the page considerably and reduced a lot of the server calls from the page.</p>
  
  <p>At the same time, I've also been looking at the RESTful ASP.NET WebAPI for some of the server-side methods, with the real beauty being that it allows to create an API for external applications at the same time that I develop the core application (which will be important for what I'm doing).  </p>
  
  <p>It seems however, after looking at several articles and <a href="https://stackoverflow.com/questions/11427573/is-it-possible-to-create-simple-rest-services-with-signalr">these</a> <a href="https://stackoverflow.com/questions/11646918/turn-by-turn-game-use-signalr-or-both-signalr-and-rest-api">two</a> questions, that push and WebAPI methods seem like two entirely different paradigms for client-server communication.  I'm sure that I can create various methods that can be accessed via either protocol, but I'm uncertain if there are pitfalls to this or if this is considered sloppy -- maybe there's a more elegant way to achieve what I'm aiming for.  </p>
  
  <p>There are certainly situations in which I want the RESTful WebAPI to broadcast events via a SignalR hub... The opposite (SignalR ever needing to access the WebAPI) seems less likely, but I suppose still possible.</p>
  
  <p>Has anyone done this? Does anyone have any advice or tips on how to proceed?  What would be the most elegant way forward here?  </p>