You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is possible, but then we will need to traverse all sessions periodically to find timed out transfers. This may be difficult to arrange in some time-sensitive applications.
Alternatively, we could keep a view of all sessions ordered by the last update time, and check that view every time the receive function is invoked, without having to extend the API. The default timeout could be some multiple of the transfer-ID timeout. This can be done after the "significant completion" is reached.
Originally posted by @pavel-kirienko in #38 (comment)
The text was updated successfully, but these errors were encountered: