SignalR/SignalR — Issue #198: Change hubs design so that each client method is not a signal
Author: DamianEdwards
Created: 2012-02-16 19:00:30+00:00
State: open
Labels: feature

Currently, each client-side hub method creates a distinct signal that will get tripped when that method is called on the server via Clients.foo. This requires the client to gather information about all the possible methods before the connection is started and then send that data up to the server in the connectionData payload so the appropriate signals can be set up. This causes issues when you have a lot of hub methods as the total connectionData payload can push the GET URL beyond the maximum size, as well as creating many signal subscriptions in the message bus.

Rather, we should just have each hub represented by a single signal. That way, all hub client method invocations from the server will just trip the single hub signal.