title: SignalR multiple hubs on different paths in same application?
body: <p>I have an application which contains multiple hubs all on unique paths, so when calling the default :</p>
  
  <p><code>routes.MapHubs("path", new HubConfiguration(...));</code> </p>
  
  <p>It blows up saying that the signalr.hubs is already defined (as mentioned here <a href="https://stackoverflow.com/questions/16166040/maphubs-not-needed-in-signalr-1-01">MapHubs not needed in SignalR 1.01?</a>).</p>
  
  <p>Now I can understand that it should only be called once, but then you will only get 1 path, so is there any way to handle a path per hub scenario? like how with MVC you specify the controller and action? so something like:</p>
  
  <p><code>routes.MapHub&lt;SomeHub&gt;("path", new HubConfiguration(...));</code></p>
  
  <p>== Edit for more info ==</p>
  
  <p>It is mentioned often that you should never need to call this map hubs more than once, and in <em>most</em> scenarios I can agree, however I would not say that this is going to be the case for all applications.</p>
  
  <p>In this scenario it is a website which at runtime loads any plugins which are available, each plugin is exposed the dependency injection framework to include its dependencies and the route table to include its routes. The hubs may have nothing to do with each other (other than the fact that they are both hub objects). So the hubs are not all known up front and are only known after the plugins are loaded, and yes I could wait until after this and try binding the hubs there, however then how do I have custom routes for each one then?</p>
  
  <p>This seems to be a case of SignalR trying to abstract a little too much, as I dont see it being a bad idea to have custom routes rather than the default "/signalr", and as the routes all have different responsibilities it seems bad to have one entry route for them all.</p>
  
  <p>So anyway I think the question still stands, as I dont see this as being a bad use case or bad design it just seems to be that I want to be able to have a route with a hub applied to it, much like in mvc you apply a controller and action to a route.</p>