During IOCP, it is more and more feeling, in the bottom of the network, in fact, do not need too much object-oriented elements, even if I use pure C to implement an IOCP, I think it is necessary to achieve the needs of the application. It is also acceptable, and it is necessary to take care of too many additional things, such as a well-known, called "object-oriented". IOCP itself is a small core. Its own features should be as independent as possible, only responsible for the most underlying network connection, disconnection, and error prompt, as for other management, such as connection queues, management and sending data Further operation, these should not be IOCP, the minimization kernel should be made, only such things will be more widely adapted to various needs.
