Content deleted Content added
Afootsquab (talk | contribs) Citation needed template added |
Afootsquab (talk | contribs) m Citation needed template added |
||
Line 5:
OWIN aims to decouple the relationship between ASP.NET <ref name=":0" /><ref name=":1" />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, new [[Web framework]]s 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.<ref>{{Cite book |last=Freeman |first=Adam |url=https://books.google.com/books?id=FVMnCgAAQBAJ&pg=PA182&printsec=frontcover&dq=%22Open+Web+Interface+for+.NET%22+-wikipedia&newbks=0&hl=en&redir_esc=y#v=onepage&q=%22Open%20Web%20Interface%20for%20.NET%22%20-wikipedia&f=false |title=Expert ASP.NET Web API 2 for MVC Developers |date=2014-09-16 |publisher=Apress |isbn=978-1-4842-0085-8 |language=en}}</ref><ref>{{Cite book |last=Zamora |first=Jodi |url=https://dl.acm.org/doi/10.5555/3051942 |title=OWIN for IT Students |publisher=CreateSpace Independent Publishing Platform |isbn=978-1-5330-4532-4 |___location=North Charleston, SC, USA |doi=}}</ref>
In this regard, OWIN aims to do for .NET what [[Java Servlet]] and [[Servlet containers]] do for the [[Java virtual machine|JVM]]. Project Katana is a set of OWIN components built by Microsoft.{{Citation needed|date=December 2024}}
== OWIN as middleware ==
| |||