Learn to Use ASP.NET 4.5 WebSockets The Easy Way
Building Real-time Web Apps with ASP.NET WebAPI and WebSockets
Learn About ASP.NET SignalR
Tutorial: Getting Started with SignalR 2.0
Signalr Supported Platforms
“Supported server operating systems
The SignalR server component can be hosted in the following server or client operating systems. 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).
Windows Server 2012
Windows Server 2008 r2
Supported server .NET Framework version
SignalR 2 is only supported on .NET Famework 4.5. See the Recommended Updates section for updates that enhance reliability, compatibility, stability, and performance.”
“Supported server IIS versions
When SignalR is hosted in IIS, the following versions are supported. Note that if a client operating system is used, such as for development (Windows 8 or Windows 7), full versions of IIS or Cassini should not be used, since there will be a limit of 10 simultaneous connections imposed, which will be reached very quickly since connections are transient, frequently re-established, and are not disposed immediately upon no longer being used. IIS Express should be used on client operating systems.
Also note that for SignalR to use WebSocket, IIS 8 or IIS 8 Express must be used, the server must be using Windows 8, Windows Server 2012, or later, and WebSocket must be enabled in IIS. For information on how to enable WebSocket in IIS, see IIS 8.0 WebSocket Protocol Support.
IIS 8 or IIS 8 Express.
IIS 7 and 7.5. Support for extensionless URLs is required.
IIS must be running in integrated mode; classic mode is not supported. Message delays of up to 30 seconds may be experienced if IIS is run in classic mode using the Server-Sent Events transport.
The hosting application must be running in full trust mode.”
“IIS 8.0 The WebSocket Protocol was introduced in IIS 8.0.”
How do you handle authentication via cookie with CURL?
“If you mean the username and password are entered in a form on a login page, then cURL can “submit” that form like:
curl -d “username=miniape&password=SeCrEt” http://whatever.com/login
and if you want to store the cookie that comes back you do so by specifying a cookie file:
curl -c cookies.txt -d “username=miniape&password=SeCrEt” http://whatever.com/login
and to use those cookie in later requests you do:
curl -b cookies.txt -d “username=miniape&password=SeCrEt” http://whatever.com/login
or do both if you want to both send and receive cookies:
curl -b cookies.txt -c cookies.txt -d “username=miniape&password=SeCrEt” http://whatever.com/login
Raspberry Pi + Nancy + OWIN + SignalR
My very own Taskmanager in HTML 5, SignalR and Nancy
Building a simple Nancy app from scratch using Mono and MonoDevelop in OSX
Project-less scripted C# with ScriptCS and Roslyn
Use OWIN to Self-Host ASP.NET Web API 2
Async Route Handling with Nancy
Best Practices in Asynchronous Programming