This project stalled when I determined that the differences between the various options where not very significant.
Reasons to use Kts.Remoting over SignalR:
- The SignalR project is stalled until the release of Asp.net 5 (in spring of 2016).
- I deal with pull requests quickly, and am anxious for fixes.
- Injection in Kts.Remoting is not weird; there are no global lifetimes of injectables.
- Full proxy support. (See the examples below.)
- Binary serializer support. (See the examples below.)
- Hubs are not transitive. You can use singleton services for them.
Reasons to use SignalR instead:
- You need an Asp.net 5 project now.
- You need generated Javascript proxies.
- You do fancy work with the Caller and Group contexts.