SignalR Docs Feedback - Help Mitigate Current Pitfalls #15726
Description
Useless Forethought:
Let me start out by saying that SignalR is pretty awesome I probably abuse it a little more than I should. Recently I've jumped on the .Net Core bandwagon, I've felt the cross platform abilities alone justify the switch (even though the guys over at Mono make amazing stuff I didn't always use it).
Real Question/Problem:
Anyways onto the juice, I get over to the docs and I want to know what my limitations are gonna be for the switch and I hit this brick wall.
Automatic reconnects aren't supported in ASP.NET Core SignalR
I feel like this is expressed nonchalantly as if it's not a major problem with the framework.
If the client is disconnected, the user must explicitly start a new connection if they want to reconnect.
Here's what I think when I see this: In most applications today we face many different types of clients from many different types of connections (think cellular, wifi, ethernet, etc). Some of these clients can connection hop from one type of connection to another and do this often for bandwidth, powersaving, etc. This means clients could be technically disconnecting a lot.
I don't want to waste my time testing to see how much of an obstacle this is going to be, I feel as if this should be discussed a little bit more -or provide some sort of background on how to mitigate this issue.
Anyways just my 2𝇍