一个通过POP3收邮件的VC＋＋工程,可以将email附件解开

Windows网络编程第二版补充材料,包含原代码与书中没有的NetB方面的介绍，是清华大学出版的.NET丛书里的-Network Programming Windows version of the second supplementary materials, and include the original code book not NetB the presentation, is published by the Tsinghua University. The NET Series

所有网卡的地址都能获得，程序简单明了，还不快下-address all card access, procedures simple and clear, not under fast? ?

使用winpcap的dump udp数据-winpcap use the data dump udp

多个基本的数电实验工程，代码及分析都有，是初学者的好材料-More than a few basic electrical test engineering, and analysis of the code has is a good material for beginners

局域网内的点对点文件传输,运行前请先关闭防火墙.服务端和客户端要都启动-LAN peer-to-peer file transfer, run before the closure of the firewall. Server-side and client to have to start

网络工具，局域网里传文件和压缩包很快的-network tools, LAN-compressed files and quickly

Client程序同样分别创建一个TCP socket 和一个UDP socket，首先client使用TCP socket连接TCP Server。 连接成功后显示提示信息； 然后client端向TCP Server发送“GET UDP PORT”字符串，Server收到后向client回送自己的UDP Server 端口号（即Client端仅知道TCP Server的端口号而不知道UDP Server的端口号）； client在收到UDP Server的端口号后, 为用户显示3个选项： 1．“Get current time（TCP）”服务器时间 2．“Echo Mode（UDP）”回显6 3．“Exit the program”. -Client program also creates a TCP socket, respectively, and a UDP socket, the first client to use TCP socket connection TCP Server. After a successful connection displays a prompt message and then client-side to the TCP Server sends " GET UDP PORT" string, Server receipt back to the client to send their UDP Server port number (ie, Client-side only to know the TCP Server" s UDP port number do not know Server" s port number) client received UDP Server port number, in order to the user three options: 1. " Get current time (TCP)" server time 2. " Echo Mode (UDP)" echo 63. " Exit the program" .

Window下的select方式网络程序的范例-Window select the mode network programming paradigm

It is a socket server. It accepts a connection from client and prints on the console a message that client writes

SOCKET 底层协议数据结构 如： /* IP Header RFC-791 0 3 7 15 31 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Version| IHL |Type of Service| Total Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Identification | Flags | Fragment Offset | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time to Live | Protocol | Header Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options | Padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ */-SOCKET underlying protocol data structures such as:/* IP HeaderRFC-7910 3 7 15 31+-+-+-+-+-+-+-+-+-+-+-2B !-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+ | Version | IHL | Type of Service | Total Length |+-+-+-+-+-+-+-+--+-+-+-+-+-+-+-+-+-+-+