Skip to content

Kestrel's transport abstractions have been removed and made public #14881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mkArtakMSFT opened this issue Oct 1, 2019 · 0 comments · Fixed by #15044
Closed

Kestrel's transport abstractions have been removed and made public #14881

mkArtakMSFT opened this issue Oct 1, 2019 · 0 comments · Fixed by #15044
Assignees
Labels
breaking-change Indicates a .NET Core breaking change

Comments

@mkArtakMSFT
Copy link

mkArtakMSFT commented Oct 1, 2019

Kestrel's transport abstractions have been removed and made public

As part of moving away from pubternal APIs the Kestrel transport layer APIs are now exposed as a public interface(s) in the Microsoft.AspNetCore.Connections.Abstractions library

Version introduced

3.0

Old behavior

  • Transport related abstractions were available in the Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions library
  • The ListenOptions.NoDelay property was available

New behavior

  • The IConnectionListener interface was introduced in Microsoft.AspNetCore.Connections.Abstractions library to expose the mostly used functionality from the ...Transport.Abstractions library
  • The NoDelay is now available in transport options (LibuvTransportOptions and SocketTransportOptions)
  • SchedulingMode is not available any more

Reason for change

In ASP.NET Core has moved away from pubternal APIs

Recommended action

Category

ASP.NET Core

Affected APIs

 Not detectable via API analysis

Issue metadata

  • Issue type: breaking-change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates a .NET Core breaking change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants