[Kestrel] Tooling around connection refused on app restart

Question

[Kestrel] Tooling around connection refused on app restart

BrennanConroy opened this issue 5 years ago · 4 comments

Dev inner-loop holding sockets on restart (so connections don't fail)
~~SNI based Multi-tenancy~~
Tooling, editor owns L4 proxy
Related: switching VS from IIS Express to Kestrel

Answer 1 · 2020-11-02T22:13:48.000Z

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Answer 2 · 2021-01-26T17:18:24.000Z

FYI I have a prototype that will fix this problem on Windows. It involves have a parent process hold onto a socket for the duration of the lifetime of the dotnet app running. shirhatti/zocket#1. There are few caveats, but in comparison to the L4 proxy this is a much safer and better approach.

Answer 3 · 2021-03-18T18:49:58.000Z

This was punted for now pending data from about how frequently full rebuilds will be necessary.

Answer 4 · 2021-03-18T18:50:05.000Z

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.