4 ms·
Thank you very much for your comment! I don't have any issues with the IHost and builder patterns. I actually like those - although I've only used the very bas
by drdaeman 4y ago
Thank you very much for your comment!
I don't have any issues with the IHost and builder patterns. I actually like those - although I've only used the very basics, so I don't really know about the intricacies and possible drawbacks.
Thanks for clearing my misunderstanding about the coupling. I really thought Kestrel was something different, have not expected it to be this high level. It being a replacement of HTTP.sys totally makes sense, of course.
I've found and read https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis/middleware https://learn.microsoft.com/en-us/aspnet/core/fundamentals/m... and it started to make more sense now.
- WorldMaker 4y agoThere's an ancient historic low-level API, that I just remembered, which you can explore that still remains around for backwards compatibility but isn't recommended for new code: Kestrel was (via a long scenic route) forked from System.Net.HttpListener [1] which is the closest to a strict bare-bones HTTP.SYS wrapper that has existed in .NET. There's a long issues thread on HttpListener should be more strongly marked deprecated [2] to avoid people accidentally using it despite today's recommendations to use Kestrel/the "Most Core" parts of ASP.NET. One fun part of the thread is an example repo of the absolute most "bare-bones" and "raw" Kestrel bootup possible [3], including a "TODO: implement TLS handshake here" bit. [1] https://learn.microsoft.com/en-us/dotnet/api/system.net.httplistener?view=net-7.0 https://learn.microsoft.com/en-us/dotnet/api/system.net.http... [2] https://github.com/dotnet/platform-compat/issues/88 https://github.com/dotnet/platform-compat/issues/88 [3] https://github.com/davidfowl/BasicKestrel/tree/master/BasicKestrel https://github.com/davidfowl/BasicKestrel/tree/master/BasicK...