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
Given a message is generated for transport to another node and no peers are available, how does the node queue the message?
Solution
One possible solution is to include a protocol with a naive default reference implementation of an in-memory cache & provide a method to extend or override by an implementing client
Acceptance criteria
Nodes generate messages for peers in an offline state that are eventually transmitted to any other peer
The text was updated successfully, but these errors were encountered:
Problem
Given a message is generated for transport to another node and no peers are available, how does the node queue the message?
Solution
One possible solution is to include a protocol with a naive default reference implementation of an in-memory cache & provide a method to extend or override by an implementing client
Acceptance criteria
Nodes generate messages for peers in an offline state that are eventually transmitted to any other peer
The text was updated successfully, but these errors were encountered: