Several suggestions on code refactoring

The project is finished, and the skeleton is basically clear.CodeRebuild and optimization, sort out several points, and welcome to supplement and correct them. Thank you very much!

1. Try not to use public. For classes or methods that must be made public, make sure they are at least one of the following:
A. Data objects, including databases and script templates
B. unified access portal for public modules
C. Protocol definitions for broad scopes such as enumeration, exceptions, and interfaces

2. Code comments should be slightly higher than average within a specific logic implementation class
3. Use the Message Processing Mechanism with caution and rethink the logic coupling. When the message processing mechanism must be used, ensure that the registered processor is released at the appropriate time, unless you have enough reason to make it an object with a long life cycle
4. Finally, regardless of the size of the refactoring, if you already have a unit test case, please use the unit test to check your results after completing the case. It will tell you some potential risks.