In today's maintenance process, the task cannot be triggered. The problems involved are:
- Task acquisition is triggered by the client, which leads to this possibility. If all tasks are implemented on the server, this problem will not occur.
- Ensure the uniqueness and completeness of data blocks. because the number of tasks, the completion mark, and the current completion progress are sent at different times, the client's data on the server must be trusted;
Lessons learned
- We need to focus on testing to solve some data resetting problems during the cross-day period. Is it a simulated interface that can be done without restarting the server?
- Task receiving is triggered by the server.
- The data of each logical unit must be processed by a unified interface; or, if traffic is not considered, data is sent out in a unified manner. For example, a part of the structure is not sent out.
- When sending attribute data of an object, the object must exist to avoid ambiguity on the client.
One game Fault Handling