The Open Web Interface for .NET (OWIN)
OWIN is a set of practices and libraries which let you acquire control over all parts of your application's lifecycle. It provides hooks for a developer to have impact on the environment the application runs in and not only the application itself. It also lets you implement custom functionality and plug it into the pipeline at any point in the request lifecycle.
1. OWIN is a framework which lets you hook into and control the hosting environment and request pipeline of your application. It can replace IIS altogether, or work with it side by side.
2. OWIN can replace IIS, but does not need to. It can plug components in all parts of the pipeline. Some of these can be a host process for the web app (which would replace IIS), but others can be additional functionality (like authentication). It is all up to the developer.
3. If you are using ready-made components (which is what Katana is), then some parts of the application functionality are much easier to implement compared compared to old ASP.NET. Authentication with third-party identity providers (Facebook, Twitter) is one example of this.
4. OWIN is essentially a collection of best practices, which have been proven in web development communities. It shows a way to implement web apps which is very open to extensibility. As each web developer should constantly be on the cutting edge of new technologies, this is one way to stay up to date with the whole web development community and not just .NET. If you learn OWIN, it would be much easier to learn other web development frameworks like Express for node.js or Rack for Ruby, because the practices they use are similar.
No comments:
Post a Comment