Open Web Interface for .NET: Difference between revisions

Revision as of 11:19, 22 August 2015

Revision as of 01:37, 29 November 2015

Line 7:

== OWIN as middleware ==

In addition to decoupling web frameworks and web servers, OWIN allows chaining together [[middleware]] 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. This allows infrastructure concerns, such as [[authentication]], 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. This allows them to be reused in other web frameworks, and also ensures a cleaner separation from the application using them.

== See also ==

*[[HTTP handler]]

== External links ==

Line 13 ⟶ 16:

* [https://www.nuget.org/packages?q=owin NuGet packages relating to OWIN]

{{Web interfaces}}

[[Category:Free software]]

[[Category:Free software]]

{{web-software-stub}}