I want to use SignalR selfhosted with Owin.
What are the differences between these two packages:
Microsoft ASP.NET SignalR OWIN
and
Microsoft ASP.NET SignalR Self Host
When to use one or other?
OWIN is the base of the SignalR library. You also know that OWIN is used to do a decoupled architecture between the web server and web application, from this great feature OWIN is the ideal feature to self-host a SignalR application. The following are reasons to not host in IIS: The availability of IIS.
SignalR is deprecated. May I know the latest package for the same. - Microsoft Q&A.
ASP.NET Core SignalR is a library that simplifies adding real-time web functionality to apps. It uses WebSockets whenever possible. For most applications, we recommend SignalR rather than raw WebSockets.
OWIN allows web apps to be decoupled from web servers. It defines a standard way for middleware to be used in a pipeline to handle requests and associated responses. ASP.NET Core applications and middleware can interoperate with OWIN-based applications, servers, and middleware.
Microsoft ASP.NET SignalR Self Host
still uses OWIN to startup. The only difference is that the Self Hosted SignalR server doesn't need to be nested in an ASP.NET web application hosted in IIS. It can be a simple console application.
See MSDN for more info:
Reasons for not hosting in IIS include:
I think the main difference is, that Microsoft ASP.NET SignalR OWIN
is an older package, because it depends on Microsoft.AspNet.SignalR.Core (>= 1.2.2)
. And Microsoft ASP.NET SignalR Self Host
depends on Microsoft.AspNet.SignalR.Core (>= 2.2.0)
. That is why I will use the Microsoft ASP.NET SignalR Self Host
package.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With