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
With xaya/xaya#91 (also backported to 1.2), Xaya Core now supports publishing ZMQ notifications about pending moves. We should check whether that is enabled in getzmqnotifications and if it is, support processing them and forwarding to game-specific callbacks.
The text was updated successfully, but these errors were encountered:
We will add a new interface PendingMoveProcessor, which has two methods Clear and AddPendingMove. The first one will be called whenever a new block comes in, and then moves that are still pending as well as pending moves that come in over time will be added with the second method.
Concrete GSP implementations can then (if they want to) pass an instance of PendingMoveProcessor to Game, and have it process moves based on their needs.
With #84 done, all that remains is actually using the pending moves exposed by a GSP in a channel daemon. This is work in progress, but currently blocked on the issue mentioned in the previous comment. It is not very important, though.
With xaya/xaya#91 (also backported to
1.2
), Xaya Core now supports publishing ZMQ notifications about pending moves. We should check whether that is enabled ingetzmqnotifications
and if it is, support processing them and forwarding to game-specific callbacks.The text was updated successfully, but these errors were encountered: