SignalR will still work without WebSockets, it will fall back to long polling I believe.
Craig On Wed, Apr 8, 2015 at 10:50 AM, Greg Keogh <g...@mira.net> wrote: > Folks, our ASP.NET app can submit a job to the server for processing > which can take up to a minute or so. We've been looking at ways the client > can see "progress" on the server-side: * AJAX script could poll at > intervals by calling a web service method * A kit like SignalR could push > notifications to the client. SignalR is of course the most elegant and > attractive option, but HERE > <http://www.asp.net/signalr/overview/getting-started/supported-platforms> > I see this note about using WebSockets as the preferred transport: > > *... Note that for SignalR to use WebSockets, Windows Server 2012 or > Windows 8 is required (WebSocket can be used on Windows Azure Web Sites, as > long as the site's .NET framework version is set to 4.5, and Web Sockets is > enabled in the site's Configuration page).* > > We don't have a 2012 server or Win8 dev machine at the moment. Using Azure > is a future possibility but we'd have to investigate how to deploy a > Kentico <http://www.kentico.com/> site to Azure. So there are many > irritating overlapping issues to get SignalR working. > > Any general comments on this "web server push" idea this would be welcome. > > *Greg K* >
