Open analogrelay opened 5 years ago
Pre-triage notes:
We'll take a look at this among post-3.0 work (including things like seemless reconnect) and aim to do it in 3.1 if that's appropriate.
Any update, on when the automaticReconnect will be scheduled? It's obviously not part of the 5.0 RC.
@BrennanConroy Since the "5.0-candidate" label was removed, and it's not part of the 5.0 release, what's the plan with this feature?
Hello, any updates on when this will be release for Java clients?
Thanks for contacting us.
We're moving this issue to the Next sprint planning
milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
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.
Since it's been moved to the backlog end of July and has been there since, I guess it's not going to happen very soon, right @BrennanConroy @davidfowl ?
Is there any news about the feature? I'm using 7.0.0-preview.4.22251.1 and client reconnect would be much appropriate
Hello, any updates on when this will be release for Java clients?
Any updates on this?
Epic #8797
Split from https://github.com/aspnet/AspNetCore/issues/5282
We will support automatic reconnect in 3.0 without message replay. We will also allow customization of the reconnect logic. This will be opt-in via a
HubConnectionBuilder
option. The default behavior will continue to be manual reconnection.