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
Breaking change: Blazor StateManager does not use the provided timeout parameter #3800
Comments
This is left over from the original design before the final 8.0.0 release. I suppose a timeout still is a valid concern. And for |
I'm working on this issue, shoudn't we change ISessionManager to receive a cancellation token also? public interface ISessionManager
{
Task<Session> RetrieveSession(TimeSpan timeout);
Task<Session> RetrieveSession(CancellationToken ct);
Session GetCachedSession();
Task SendSession(TimeSpan timeout);
Task SendSession(CancellationToken ct);
} |
I woul say: no. |
I created with both options this way @StefanOssendorf can comment on my work and I can finish it the way will work best |
csla/Source/Csla.Blazor/State/StateManager.cs
Lines 46 to 52 in 881c262
As shown the timeout parameter is not used in this method. The method is called by the two
InitializeAsync()
methods where one provides a timeout parameters as well.I think we have two ways to correct this:
InitializeAsync(TimeSpan)
method.ISessionManager.RetrieveSession()
with an overload which also accepts a timeout and pass it alongI think option 2 would be the best so the user can decide whether he wants to wait or not.
In this regard: Should the
SaveState
also get a timeout parameter with passing along toSendSession()
?The text was updated successfully, but these errors were encountered: