With regard to question "Could we use WSHttpBinding with Request-CallBack (also called Duplex) exchange pattern?", couldn't we implement a long poll with WSHttpBinding? Such a solution would be firewall friendly but would require timeouts on the server to be adjusted, the maximum allowable connections would need to be adjusted, and any threadpool settings would need to be carefully considered.
With regard to "What replaces WCF in .Net Core?", I would make special mention that gRPC seems to be the recommended approach by Microsoft (Interview with Scott Hunter). I also would say that replacing WCF should not simply aim to find a small, relatively inactive Open Source project that re-implements WCF on .NET Core. Evaluating other communication frameworks requires a deeper discussion about how to select an appropriate technology to be the basis of your communications. It is clear that WCF is dead and I think projects should be considering moving to either HTTP APIs, gRPC, or even SignalR (based on Websockets). It should also be noted that client-side WCF looks like it could be supported dotnet/WCF.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
With regard to question "Could we use WSHttpBinding with Request-CallBack (also called Duplex) exchange pattern?", couldn't we implement a long poll with WSHttpBinding? Such a solution would be firewall friendly but would require timeouts on the server to be adjusted, the maximum allowable connections would need to be adjusted, and any threadpool settings would need to be carefully considered.
With regard to "What replaces WCF in .Net Core?", I would make special mention that gRPC seems to be the recommended approach by Microsoft (Interview with Scott Hunter). I also would say that replacing WCF should not simply aim to find a small, relatively inactive Open Source project that re-implements WCF on .NET Core. Evaluating other communication frameworks requires a deeper discussion about how to select an appropriate technology to be the basis of your communications. It is clear that WCF is dead and I think projects should be considering moving to either HTTP APIs, gRPC, or even SignalR (based on Websockets). It should also be noted that client-side WCF looks like it could be supported dotnet/WCF.