资 源 简 介
Testing TCP and UDP socket servers using C# and .NETWhen you re developing a TCP/IP server application it s easy to test it poorly. It s easy to fire requests into a server, check the responses and assume that s enough. Even if you re testing using the actual production client application you may find that you are failing to fully test the server under heavy load or unusual network conditions. You may be using two or more machines, but your development network probably doesn t cause the kind of packet fragmentation and delays that you might encounter in the wild. Often when testing in the development environment your server only ever receives complete, distinct messages, and this can lead novice developers to assume that this is how it always is. As we pointed out in a previous article, the server developer is always responsible for breaking up the TCP byte stream into protocol specific chunks.
