The first is a painting flow chart, and it feels that it is still basic.
.
Why do you say this way?
The first, the diagram of the words is completely ideologically, and cannot be implemented on the program. It can be said that it is too much attention to the analysis of business processes without combining the characteristics.
Second, the modifications are too frequent, draw one, and modify it. Still not enough abstraction on real problems.
I feel that the picture is too trouble, and I will first painted on the draft in the future, and I'm going to go. The mouse point is in the mouse ~~~ Waiting for the basic skill, painting directly on the computer.
Yesterday, I realized Server with Java. Today, I use VC to realize the client. The overall feeling is not bad, at least the program written is clear enough, implies this OO idea ~~ and process design is different. There is also the start of the working principle of Socket at the beginning. Java is better than MFC, simple, but current writing procedures still uses MFC, feeling more complicated with API! Not practical. Only as examples of teaching.
Finally, I will go back to Receive Data after reeive Data, so that I want to leave the corresponding time and network delay, think about it.
I am here today, I don't want to write a text.
