-
Notifications
You must be signed in to change notification settings - Fork 39
[Announcement] WebListener packages and APIs merged and renamed #289
Comments
Will this repo be renamed to "HttpSys" as well? |
Not right now. We'll continue to use WebListener as the project codename. |
We should probably rename the repository as well /cc @Eilon |
Just don't name it flat HttpSys, that would be too confusing. HttpSysIntegratoin like IISIntegration? |
Let me know and I'll rename it... GitHub will auto-redirect everything so it's quite safe. |
Why not? https://github.com/tjanczuk/httpsys 😄 HttpSysIntegration is fine. |
Let's get confirmation from @DamianEdwards and I'll rename. |
Is HttpSysServer any better? It mirrors KestrelHttpServer. |
I like it better |
HttpSysServer |
DONE. |
One additional change: Direct WebSocket support has been removed from this new package. The application must now add the WebSocket middleware for WebSocket support. This mirrors the Kestrel architecture. There should not be any functional changes because the two components were previously sharing the same implementation code. See https://github.com/aspnet/WebSockets/blob/b996ee39a429479e0bc301d198007cd85cc2acbd/samples/EchoApp/Startup.cs#L34 and the Microsoft.AspNetCore.WebSockets package. |
We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have. |
The packages
Microsoft.AspNetCore.Server.WebListener
andMicrosoft.Net.Http.Server
have been merged into a new packageMicrosoft.AspNetCore.Server.HttpSys
. The namespaces have been updated to match.The WebHostBuilder extension has similarly been renamed from
UseWebListener
toUseHttpSys
. The options for this extension have been flattened as shown here.The low level WebListener API has been removed to avoid duplication and confusion with HttpListener which has recently been added to .NET Core.
A few more consolidations and optimizations will follow, as discussed here: #283. The discussion issue will be updated accordingly with any additional breaking changes.
The text was updated successfully, but these errors were encountered: