Content deleted Content added
Afootsquab (talk | contribs) m Citation needed template added |
Afootsquab (talk | contribs) New reference added |
||
Line 10:
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.<ref>{{Cite web |last=Praburaj |date=2022-09-30 |title=OWIN Middleware in the IIS integrated pipeline |url=https://learn.microsoft.com/en-us/aspnet/aspnet/overview/owin-and-katana/owin-middleware-in-the-iis-integrated-pipeline |access-date=2024-12-04 |website=learn.microsoft.com |language=en-us}}</ref>
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.<ref>{{Cite web |last=howarddierking |date=2023-06-15 |title=An Overview of Project Katana |url=https://learn.microsoft.com/en-us/aspnet/aspnet/overview/owin-and-katana/an-overview-of-project-katana |access-date=2024-12-04 |website=learn.microsoft.com |language=en-us}}</ref> This allows them to be reused in other Web frameworks, and also ensures a cleaner separation from the application using them.
== See also ==
| |||