| OWIN | |
|---|---|
| Original author | Community-owned |
| Developer | OWIN Community |
| Written in | C# |
| Operating system | Cross-platform |
| Platform | .NET Framework,.NET Core |
| Type | Web server interface |
| License | Open-source |
| Website | owin.org |
OWIN (Open Web Interface for .NET) is a standard for an interface between .NET Web applications and Web servers.[1] It is a community-owned open-source project. Prior to OWIN, Microsoft'sASP.NET[2] technology was designed on top ofIIS, and Web applications could not easily be run on another Web server (although note that despite this the Mono community developed several ASP.NET compatible Web servers, such asXSP).[citation needed]
OWIN aims to decouple the relationship between ASP.NET[1][2]applications and IIS by defining a standard interface. Developers of Web servers can be sure that, if they implement OWIN correctly, ASP.NET applications will run on their server. Similarly, newWeb frameworks could be developed as an alternative to ASP.NET. As long as they target OWIN, they will run on any OWIN compatible Web server, including IIS.[3][4]
In this regard, OWIN aims to do for .NET whatJava Servlet andServlet containers do for theJVM. Project Katana is a set of OWIN components for ASP.NET (.NET Framework) built by Microsoft.[citation needed] ASP.NET Core (.NET) has its own middleware system that is similar to OWIN.
In addition to decoupling Web frameworks and Web servers, OWIN allows chaining togethermiddleware into a pipeline. A Web framework can interact with OWIN without knowing whether it is interacting directly with the underlying web server, or with one or more layers of middleware (each implementing OWIN) on top of the Web server.[5]
This allows infrastructure concerns, such asauthentication, to be split out into separate modules. This is desirable as it decouples them from the application's own code, and makes them reusable across applications. In Project Katana, Microsoft has made into OWIN modules several ASP.NET features that were previously part of the core ASP.NET framework.[6] This allows them to be reused in other Web frameworks, and also ensures a cleaner separation from the application using them.