ZFQXOX

一个与MyIE功能相同的多窗口浏览器，相当实用，包含全部源代码，强烈推荐( With the MyIE function same multi- windows browser, is quite practical, contains the complete source code, intense recommendation! )

获取本地计算机信息的小代码，比较简单，适合初学网络编程(a simple program of geting information from computer)

类似Windows的netstat程序的程序 (An app which is like to windowss netstat)

TCP协议数据传输和聊天程序服务器端程序源代码(TCP data and message transferring, server program.)

SOCKET编程规范(SOCKET programming specification)

实现网络抓包功能的基本原理与抓包实现方法，是个不错的提示(for sniffer)

11mh的辅助源码，下载研究去吧！！！！(Source of the 11mh the secondary, download study go! ! ! !)

多协议文件传输c/s网络应用设计与实现,程序用 TCP/UDP 两个协议模拟多协议服务器。首先服务器端要将两种协议的套接字创建好，并且监听 TCP 端口的连接。必要时使用select函数来进行多连接处理和非阻塞处理。而客户端直接可以按照发送的地址和端口号来进行通讯。 首先要运行服务器端，服务器会监听 TCP 端口。然后运行客户端，根据事先设定好的 IP和端口，就可以进行连接传输数据了。 程序实现的关键步骤： 以TCP协议为例 服务器端： 1.创建套接字；2.绑定端口；3.进入无穷的循环；4.接收请求；5.处理请求；6.应答。 客户端： 1.找到服务器的IP地址和协议的端口号；2.创建套接字；3.确定连接需要任意的，没有使用的端口号允许TCP去选择一个；4.将套接字和服务器连接；5.使用应用层协议和服务器交互；6.关闭连接。 (Multi-protocol file transfer c/s network application design and implementation of programs simulate multi-protocol server with TCP/UDP both protocols. First socket server to create a good two protocols, TCP port and listens for connections. If necessary, use the function to handle multiple connections and non-blocking treatment. And the client can follow directly address and port number to communicate. First run on the server side, the server listens on TCP port. Then run the client, according to pre-configured IP and port, you can connect the data transmission. The key step program implementation: In TCP protocol as an example Service-Terminal: 1. Create a socket 2 bound port 3 enter an infinite loop 4. receiving a request 5. processing requests 6 response. Clients: 1. Locate the server s IP address and protocol port number 2 creates a socket 3 connections need to determine arbitrary, unused port allows TCP to choose a 4 and the socket server connections 5 using appli)

免注册QQ/MSN号码,直接在网页上聊天/通话/视频,最佳在线客服.(Live Support)

Currently, most of people use MS DCOM/COM+, Java Bean/RMI, and Corba to do distributed computing over internet. All of these technologies are provided with some tools and intermediate objects to simplify internet development. However, these technologies have one common and fundamental problem that all of the calls between a client and a server are blocked for a returned result (please correct me if this is wrong). A client stays still, and has to wait for a while after sending a request to a server. If the request is a lengthy action, the client application seems to be dead to a user. In most cases, we could use a worker thread at the client side to do background computation for solving this problem. However, this comes with an expensive price, more coding, data synchronization and mess in coding logic. Additionally, I also doubt that these technologies are able to really move data across internet efficiently.