SIGNALR supports a variety of server and client configurations. In addition, each mode of transmission has its own requirements, and if some transmission mode is not supported by the system, SIGNALR can gracefully failover to other types of transmission mode. For more information about the transport modes supported by SIGNALR, see: Transports and Fallbacks.
System Requirements
The SIGNALR server component can be supported by a variety of server configurations. This section describes the operating systems that are supported. NET Framework, IIS, and other components.
Supported server operating systems
SIGNALR server components are supported by the following server and client operating systems.
Windows Server 2012
Windows Server 2008 R2
Windows 8
Windows 7
Windows Azure
Note that if you want SIGNALR to use the webcosket, you need a Windows Server 2012 or Windows 8 operating system (WebSocket can also be supported by Windows Azure Web site, provided the site is. NET Framework version is 4.5, and websockets is already enabled on the configuration page.
Supported servers. NET Framework version
SIGNALR 2.0 supports. Net Framework 4.5 only, checking recommended updates to improve reliability, compatibility, stability, and performance.
Supported versions of server IIS
SIGNALR is supported by the following versions of IIS.
IIS 8 or IIS 8 Express.
IIS 7 and IIS 7.5 require extensionless URL support.
IIS must be running in Integrated mode and does not support Classic mode. When IIS is running in Classic mode, using the server to send events can result in 30 seconds of message latency.
The managed application must be running in trust mode.
Note that if you are using a client operating system, such as for development (Windows 7 or 8), you should not use the full version of IIS or Cassini. Because the client has 10 concurrent connections, it is very easy to reach this limit because the connection is very short and is often re built. And will not be destroyed immediately after the connection has been used. You should use IIS Express.
Also note that if you want to signalr use WebSocket, you must use IIS 8 or IIS 8 Express, the server must use Windows 8, Windows Server 2012, and IIS must have WebSocket enabled, About enabling WebSocket in IIS, see IIS 8.0 WebSocket Protocol Support.
Client system Requirements
SIGNALR can be used on a variety of client platforms. This section describes the system requirements for SIGNALR in Web browsers, Windows desktop applications, Silverlight applications, and mobile devices.
Web browser
SIGNALR can be used in a variety of web browsers, but in general, only the latest two versions are supported.
Applications that use SIGNALR in a browser must use the jquery version 1.6.4, or a major version (such as 1.7.2,1.8.2,1.9.1, etc.).
SIGNALR is available in the following browsers:
IE8, 9, 10, 11 desktop and mobile, Win8 Modern, versions are supported.
Firefox: Current version -1,win and Mac version.
Chrome: Current version -1,win and Mac version.
Safari: Current version -1,mac and iOS version.
Opera: Current version-1, only win version.
Android Browser.
In addition to the browser requirements, SIGNALR use of the transmission method also have their own requirements, such as the following table:
Transmission mode |
Ie |
Chrome (Win or iOS) |
Ff |
Safari (OS X or iOS) |
Android |
WebSockets |
10+ |
Current-1 |
Current-1 |
Current-1 |
does not support |
Server-sent Events |
does not support |
Current-1 |
Current-1 |
Current-1 |
does not support |
Foreverframe |
8+ |
does not support |
does not support |
does not support |
4.1 |
Long Polling |
8+ |
Current-1 |
Current-1 |
Current-1 |
4.1 |