I've seen signalR vs html5 websockets for asp.net MVC chat application but it doesn't 100% answer my question as it's based around HTML5 WebSockets, which Microsoft may have extended upon in .NET 4.5 with their WebSocket object.
I'm wondering if the WebSocket feature does actually do the same as SignalR and fall back to long polling when WebSockets aren't available? Surely Microsoft would implement the same technology as SignalR in their approach to this technology?
For anyone else wondering about this, I found this comment the most helpful to understand the scenario and why I'll be using SignalR:
Well, they are not really. Up until now IIS and ASP.NET didn't have
anything built in that supported WebSockets so SignalR project had to
build it themselves. Now that Microsoft is providing the plumbing
SignalR could easily switch to using Microsoft's implementation,
either in addition to or instead of their own. SignalR is an
abstraction over implementation details, WebScockets class is the
I'm wondering if the WebSocket feature does actually do the same as SignalR and fall back to long polling when WebSockets aren't available?
WebSockets is a new protocol independent of other communication techniques. From the RFC
The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or s and long polling).
Surely Microsoft would implement the same technology as SignalR in their approach to this technology?
Not if they want to conform to the specification they won't. There's certainly nothing stopping Microsoft from developing a higher level API similar to SignalR that would abstract away communication detail and offer graceful fallback. However that hypothetical API would probably build on top of WebSocket class as opposed to replacing it.