4 ms·
Could someone explain why "ASP.NET Core 1.1" Kestrel webserver decided to use LibUV DllImpor [1] instead of .NET Asynchronous Server Socket (System.Net.Socket
by skyde 10y ago
Could someone explain why "ASP.NET Core 1.1" Kestrel webserver decided to use LibUV DllImpor [1] instead of .NET Asynchronous Server Socket (System.Net.Sockets) [2].
Does that mean that the managed implementation of Async socket is broken and was too slow?
[1] "https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNetCore.Server.Kestrel/Internal/Networking/Libuv.cs" https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic...
[2] https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110).aspx https://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110)....
- davidfowl 10y agoTiming. When we started ASP.NET cross platform there were not cross platform sockets. That came much later. We'll likely move back to sockets in the future (we're actively looking at this).