When the user clicks Battle in the game, it's expecting the server to do a match making for PvP.
However, the server itself has to keep track on the user how is online and ready to play the game.
Calling just one method to get the PVP on the backend isn't enough because the transaction has to be broadcasted to the all the nodes, to update the user status first. If we also do the look up in this function, the transaction will be blocked and the user won't get updated status -- needed when the server looking up.
We can archive this using websocket subevent.
Create FindMatch endpoint: Basically, this endpoint will create a transaction to the blockchain saying that the user is online. And just return. What this endpoint returns is the topic name.
The client subscribes to the topic name returned from the server, listening for event message from the server.
Another user calls RegisterPVP endpoint, the server looks up and found the first player and emits the events to both users with the topic name in 1.
phoorichet
commented
6 years ago
When the user clicks
Battlein the game, it's expecting the server to do a match making for PvP. However, the server itself has to keep track on the user how is online and ready to play the game.Calling just one method to get the PVP on the backend isn't enough because the transaction has to be broadcasted to the all the nodes, to update the user status first. If we also do the look up in this function, the transaction will be blocked and the user won't get updated status -- needed when the server looking up.
We can archive this using websocket subevent.
ref:
Tasks: