Using Owin to get the Web project out of IIS is really special .....
Thus, a new communication channel can be derived, and the local server is self-hosted.
1 node. js
2 Python
3 Ruby
4 Owin (C#--katana project katanaproject.codeplex.com)
Although a cross-platform based on the. NET Framework core is published. But XP +ie 6 is cancer! So cross-platform is good. But the best span is indeed the. NET Framework 4.0!!!!!!!!!!!!!
Owin to some extent into the. NET Core project. After 3.0, start ignoring. NET 4.0 .... Fortunately, the open source .....
- microsoft.owin– provides a set of auxiliary types, as well as various abstract types that are built to simplify the creation of Owin components.
- Microsoft.owin.diagnostics– provides a variety of middleware components to assist in the development of Owin-based applications.
- microsoft.owin.filesystems– This package provides a file system-related abstraction and implementation.
- microsoft.owin.testing– provides some helper classes for unit testing of Owin components.
- microsoft.owin.selfhost– contains some of the components necessary to host Owin-based applications in a self-specified process.
- microsoft.owin.hosting– provides the default underlying framework types that are required to host and run Owin-based applications.
- owinhost– provides a single executable program (OwinHost.exe) that allows you to host a Owin-based application run.
- microsoft.owin.cors– This package contains components that enable cross-domain resource sharing (Cors) in the Owin middleware.
- microsoft.owin.staticfiles– This package contains some Owin middleware that can handle requests from file system resources, including files and directories.
- microsoft.owin.security– contains a number of common types that are shared by a variety of different authentication middleware components.
- microsoft.owin.security.activedirectory– a set of middleware that allows applications to authenticate using Microsoft technology.
- microsoft.owin.security.cookies– allows applications to use cookie-based authentication middleware, similar to the way forms are authenticated in ASP.
- microsoft.owin.security.facebook– allows applications to support some of the middleware of the OAuth 2.0 certification workflow that Facebook uses.
- The microsoft.owin.security.google– includes a set of middleware that supports Google's OpenID and OAuth 2.0 certified workflows.
- microsoft.owin.security.jwt– a set of middleware that allows applications to protect and validate JSON web tokens.
- microsoft.owin.security.microsoftaccount– a set of middleware that allows applications to support Microsoft account certification workflows.
- microsoft.owin.security.oauth– allows applications to support middleware for any standard OAuth 2.0 certified workflow.
- microsoft.owin.security.openidconnect– middleware that allows applications to authenticate using the Openidconnect method.
- microsoft.owin.security.twitter– allows applications to support the middleware of Twitter's OAuth 2.0 authentication workflow.
- microsoft.owin.security.wsfederation– allows applications to use Wsfederation for authentication middleware.
- microsoft.owin.host.httplistener– is a Owin server that is created based on the HttpListener class in the. Net framework and is the default server currently being used for self-hosting.
- Microsoft.owin.host.systemweb– is also a Owin server implementation, but it allows Owin-based applications to run in IIS and to use the request pipeline for ASP.
Katana or Owin? Local Self-hosted
