6. bbsd and cq66 server-side transformation
In bbsd, the user module should be easier to modify. Just change the operation of writing the .PASSWD file to
the member function of the UserManage class that operates the database, but you may need to judge first. What data changes,
which function to call. The consistency of concurrent operations is guaranteed by the locking function of the database. MySQL should
support this kind of lock. The article may be more troublesome. It is enough to convert the original operation on the file into the member function of the BoardManage class of the
database.
The cq66 mode should be easier to change, maybe the original protocol for fetching articles needs to be changed. When fetching the
title of the article, the length of the article is also sent. Then the client can
progressively request the content of the article based on the size of the display area. When requesting the article, the request range must be given.
Regarding the system module layer, might it be better to make it in the form of so? (Is so equivalent to dll?
It is not easy to do. Is it necessary?). At the same time, should the system module layer be What about saving some local data?
Or should it be made into an interface like a public function? Thinking back to the UserManage class, there may be no need to distinguish privileged instructions.
All operations must provide the ID of the operation object, and the permission check is left to the service layer above to complete?
7. Preliminary test plan
To test, you must first make something. To make something, you must first have something else. . . . .
First, install the 167 system and configure mysql, then learn the C API of mysql and then build the table.
To do this plan, you must first finish writing the 5,000 lines of code for the short semester, and then review for the postgraduate entrance examination , complete the compiler homework after reviewing, and you can start working on it if you have time and don't have girls to come to me. . . . .