3 ms·

I appears that this is using HttpListener to implement the HTTP protocol: https://github.com/sisk-http/core/blob/main/src/Http/HttpServer.cs#L35 https://github

I appears that this is using HttpListener to implement the HTTP protocol: https://github.com/sisk-http/core/blob/main/src/Http/HttpServer.cs#L35 https://github.com/sisk-http/core/blob/main/src/Http/HttpSer... HttpListener, while not deprecated, is frozen and not taking new features. For example, it does not support HTTP 2. It might not be as high performance as Kestrel (the default web server in ASP.NET Core). https://github.com/dotnet/runtime/issues/63941#issuecomment-1205259894 https://github.com/dotnet/runtime/issues/63941#issuecomment-... So the authors of the framework might want to consider longer term whether layering onto of Kestrel or some other HTTP server implementation may make more sense.

Gluber 2y ago
Isn't HttpListener still windows only ? I Remember the times we used it and it relied on http.sys on windows... Or did they port it during NET/NET Core. As Kestrel has been the recommendation from NET Core 1.0 onwards.
- neonsunset 2y ago
  It appears to use Socket (which is POSIX socket's send/recv and epoll/kqueue based) and SslStream. Can't say much about HttpListener itself, but the first two are used by Kestrel (and everything else). There is Http.sys integration for Windows though. https://github.com/dotnet/runtime/blob/ac663e44b907618c631edd614231b73677843952/src/libraries/System.Net.HttpListener/src/System/Net/Managed/HttpConnection.cs https://github.com/dotnet/runtime/blob/ac663e44b907618c631ed...
- tubs 2y ago
  Httplistener has two implementations. Managed (cross platform) and http.sys (windows only). It’s “ok”. You can’t do things like re use contexts but it’s perfectly fine for throwing small backends together when you don’t want to force users to install asp runtime. I did a minimal web api around it to make life easier going between it and kestrel. If kestrel was nugettable without the asp runtime it would be a dream but it requires a lot of that aspcore infra so it is what it is.

Gluber 2y ago

Isn't HttpListener still windows only ? I Remember the times we used it and it relied on http.sys on windows... Or did they port it during NET/NET Core. As Kestrel has been the recommendation from NET Core 1.0 onwards.

neonsunset 2y ago
It appears to use Socket (which is POSIX socket's send/recv and epoll/kqueue based) and SslStream. Can't say much about HttpListener itself, but the first two are used by Kestrel (and everything else). There is Http.sys integration for Windows though. https://github.com/dotnet/runtime/blob/ac663e44b907618c631edd614231b73677843952/src/libraries/System.Net.HttpListener/src/System/Net/Managed/HttpConnection.cs https://github.com/dotnet/runtime/blob/ac663e44b907618c631ed...
tubs 2y ago
Httplistener has two implementations. Managed (cross platform) and http.sys (windows only). It’s “ok”. You can’t do things like re use contexts but it’s perfectly fine for throwing small backends together when you don’t want to force users to install asp runtime. I did a minimal web api around it to make life easier going between it and kestrel. If kestrel was nugettable without the asp runtime it would be a dream but it requires a lot of that aspcore infra so it is what it is.