On server-side, implementing your Hub is easier as you get intellisense when sending messages to clients
-Run ConsoleClient to see a demo
diff --git a/Samples_2.1.0/WebApplication/Views/Feature/PersistentConnection.cshtml b/Samples_2.1.0/WebApplication/Views/Feature/PersistentConnection.cshtml new file mode 100644 index 0000000..86376f6 --- /dev/null +++ b/Samples_2.1.0/WebApplication/Views/Feature/PersistentConnection.cshtml @@ -0,0 +1,39 @@ +Derive class Hub<T> where T is an interface containing client methods (methods you usually invoke in a C# client using hubProxy.On). The advantage is you get autocomplete on server side when typing Clients.Caller.
- +Derive PersistentConnection class to use a low-level connection API to send and receive untyped messages.
Hub method taking a long time to complete its work, now it can easily return updates as the work is getting done.
- +Derive Hub class to use a high-level connection API to enable remote method invocation and typed messages.
Use GlobalHost.ConnectionManager to send Messages using a PersistentConnection or Hub from anywhere on the same process.
+Derive Hub<T> class where T is an interface containing client methods (methods you usually invoke in a C# client using hubProxy.On). The advantage is you get autocomplete on server side when typing Clients.Caller.
+Hub method taking a long time to complete its work, now it can easily return updates as the work is getting done.
+Send messages to authenticated users by using their username instead of a connectionId.
-