ASP.NET Core中间件还是OWIN中间件? [英] ASP.NET Core middleware or OWIN middleware?
问题描述
据我了解，除了自己的本机中间件，ASP.NET Core还支持OWIN中间件(通过app.UseOwin()).
As I understand it, ASP.NET Core has support for OWIN middleware (via app.UseOwin()) in addition to its own native middleware.
ASP.NET Core中间件和OWIN中间件有什么区别?
What is the difference between ASP.NET Core middleware and OWIN middleware?
在设计新的中间件时，如何知道应将其设计为ASP.NET Core中间件还是OWIN中间件?
When designing a new middleware, how do I know if I should design it as a ASP.NET Core middleware or a OWIN middleware?
推荐答案
您的问题让我感到好奇，我想分享一下我到目前为止所学到的知识.
Your question made me curious and I would like to share, what I have learned so far.
Katana是OWIN规范的实现.在Katana 3.0版之后，该技术已完全集成到我们今天称为ASP.NET Core的Web堆栈中.
Katana is the implementation of the OWIN spec. After version 3.0 of Katana this technology has been fully integration in the web stack we know as ASP.NET Core today.
尽管此过渡与OWIN规范保持相似.尽管已进行了一些更改.为了在ASP.NET Core中使用现有的OWIN中间件，通过可选功能("app.UseOwin()")支持OWIN.
While this transition much has stayed similar to the OWIN specifications. Although some changes have been made. In order to use existing OWIN middleware in ASP.NET Core the supports OWIN by an optional feature ("app.UseOwin()").
如果您希望使用中间件ASP.NET应用程序和ASP.NET核心应用程序作为目标，那么我将使用OWIN中间件.如果您想为ASP.NET Core开发人员提供一流的公民体验，那么ASP.NET Core中间件将被认为更合适".
If you want to target with your middleware ASP.NET apps and ASP.NET core apps, then I would use OWIN middleware. If you want to give ASP.NET Core developers a first class citizen experience, then a ASP.NET Core middleware would be recognized as more "fitting".
有关ASP.NET Core中间件和OWIN中间件之间的关系的一些信息可以在这里找到:
Some information about the relationship between ASP.NET Core middleware and OWIN middleware can be found here:
- Katana, ASP.NET 5, and bridging the gap
- Katana Project
- https://docs.asp.net/en/latest/fundamentals/owin.html
这篇关于ASP.NET Core中间件还是OWIN中间件?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
