But when we deploy our ASP.NET apps, it’s invariably on an IIS server. Anyone webdev worth their salt, know that during development, you use either Cassini - the development web server, or IIS Express, the newer more robust in-process web server. We first take a step back and see how Web Applications work on ASP.NET today from a hosting point of view.
After all what is the OWIN specification for? The Microsoft Web Application Stack today With the vague idea of what is OWIN and Katana, let’s go deeper and see what is the grand scheme of things in which OWIN and Katana fit in.
#Masstransit and signalr for free
Subscribe to this eMagazine for Free Why do we need OWIN? NET professionals published once every two months. NET Magazine – A Free High Quality Digital Magazine for. Don’t worry about what those Modules do, we’ll see that soon, for now, imprint this much, OWIN is a blueprint and Katana in as implementation. So OWIN is like the blueprint whereas the Katana project uses the blueprint to create increasingly useful set of modules that adhere to the OWIN rules. The Katana project by Microsoft picks up these rules and has created an implementation of the specification. For now let’s call it as a specification of interoperability between webhosts and frameworks, that outlines ‘some’ rules for building ‘certain’ types of.
You can compare OWIN with RACK in Ruby and WSGI from the Python world. Well OWIN is an open, industry standard or a specification and is primarily authored by two members of the ASP.NET Team - Benjamin Vanderveen and Louis Dejardin. NET already has ASP.NET and MVC and Web API, how does this OWIN thing fit in? Is it a new tool/library/web framework, and then what is Katana?
0 kommentar(er)
