socket通讯常见模式分析

 

socket通讯常见模式分析（一）

最近由于工作需要，本人对socket通讯的相关信息进行了相应的归纳和整理，现将结果和大家分享一下。socket通讯在应用中主要分成两个基本类型： 阻塞I/O通信模型、非阻塞 I/O通信模型（java NIO）。

1. 阻塞I/O通信模型

首先先提供一段阻塞I/O通信模型的基本代码供大家分析：

Server端:

package com.jerry.server;
import java.io.IOException;
import java.net.ServerSocket;
import java.net.Socket;
import java.util.UUID;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import org.springframework.beans.factory.DisposableBean;
import com.jerry.util.ExceptionUtil;
/***
* Socket服务端
* @author JerryCao
*
*/
public class BatchProcessReceiver implements DisposableBean{
private int port;
private ServerSocket serverSocket;
private int poolSize;
private int timeOut;
private ExecutorService executor;
// private static Logger log= Logger.getLogger(BatchProcessReceiver.class.getName());
public void setPort(int port) {
this.port = port;
}
public void setPoolSize(int poolSize) {
this.poolSize = poolSize;
}
public void setTimeOut(int timeOut) {
this.timeOut = timeOut;
}
BatchProcessReceiver(){
}
/**spring加载*/
private void init(){
String uuid = UUID.randomUUID().toString();
try {
executor = Executors.newFixedThreadPool(poolSize);
serverSocket = new ServerSocket(port);
new BatchProcessServerThread().start();
System.out.println("-----------------------------------------------------------------");
System.out.println("UUID:"+uuid+"\nBatchProcessReceiver init succ");
System.out.println("-----------------------------------------------------------------");
} catch (IOException e) {
System.out.println("UUID:"+uuid+"\nBatchProcessReceiver init fail"+ExceptionUtil.getStackTrace(e));
System.exit(0);
}
}
public class BatchProcessServerThread extends Thread{
String uuid = UUID.randomUUID().toString();
public void run(){
while(isServerAlive()){
Socket socket = null;
try {
socket = serverSocket.accept();
//设置超时时间
socket.setSoTimeout(timeOut);
executor.execute(new BatchProcessHander(socket));
} catch (Exception e) {
System.out.println("UUID:"+uuid+"\nBatchProcessServerThread executing fail"+ExceptionUtil.getStackTrace(e));
}
}
}
}
public void destroy() throws Exception {
String uuid = UUID.randomUUID().toString();
if(serverSocket != null){
serverSocket.close();
}
System.out.println("UUID"+uuid+"\nBatchProcessReceiver destroy succ");
}
public boolean isServerAlive(){
boolean flag = false;
try{
flag = !serverSocket.isClosed();
}catch(Exception ex){
}
return flag;
}
}

 

Handler类：

package com.jerry.server;
import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.net.Socket;
import java.util.UUID;
import com.jerry.util.ExceptionUtil;
/***
*
* @author JerryCao
*
*/
class BatchProcessHander implements Runnable{
private Socket socket;
public static final int DATA_LENGTH = 4;
protected BatchProcessHander(Socket socket){
this.socket = socket;
}
public void run() {
String uuid = UUID.randomUUID().toString();
try {
InputStream input = socket.getInputStream();
String req = processIn(input);
System.out.println("-----------------------------------------------------------------");
System.out.println("UUID:"+uuid+"\n请求报文:"+req.toString().trim());
System.out.println("-----------------------------------------------------------------");
/**业务处理请求报文得到响应报文*/
String rsp =req;
System.out.println("-----------------------------------------------------------------");
System.out.println("UUID:"+uuid+"\n响应报文:"+rsp.toString().trim());
System.out.println("-----------------------------------------------------------------");
/**输出响应报文*/
OutputStream output = socket.getOutputStream();
output.write(rsp.toString().getBytes());
output.flush();
} catch (Exception e) {
System.out.println("UUID:"+uuid+"\n报文处理异常:"+ExceptionUtil.getStackTrace(e));
}finally{
try {
if(socket != null)
socket.close();
} catch (IOException e) {
System.out.println("UUID:"+uuid+"\nsocket关闭异常:"+ExceptionUtil.getStackTrace(e));
}
}
}
/**以字节的方式读取输入流中的内容
* @throws IOException */
private String processIn(InputStream input) throws IOException{
byte[] rsps = null;
if(input != null){
ByteArrayOutputStream byteOutput = new ByteArrayOutputStream();
int total =0;
int len = 0;
int length = 0;
byte[] lenBytes = new byte[DATA_LENGTH];
input.read(lenBytes);
length = Integer.parseInt(new String(lenBytes));
byte[] temp = new byte[length];
while((len = input.read(temp))>0){
byteOutput.write(temp, 0, len);//输出字节
total +=len;
if(total == length){
break;
}
}
input = null;
byteOutput.close();
rsps = byteOutput.toByteArray();
}
if(rsps == null){
return null;
}
return new String(rsps).substring(1);
}
}

 

Client端：

 

package com.jerry;
import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.net.Socket;
public class SocketClient {
/* @throws IOException */
private static String processIn(InputStream input) throws IOException{
byte[] resp =null;
if(input != null){
ByteArrayOutputStream out = new ByteArrayOutputStream();
byte[] temp = new byte[1024];
int len = 0;
while((len = input.read(temp))> 0){
out.write(temp, 0, len);
}
input = null;
out.close();
resp = out.toByteArray();
}
if(resp == null){
return null;
}
return new String(resp);
}
public static void main(String[] args) {
Socket socket = null;
try{
socket = new Socket("172.16.0.14",10212);
OutputStream output = socket.getOutputStream();
StringBuffer reqdata = new StringBuffer();
String req ="你好!";
String length = ""+req.getBytes().length;
reqdata.append(length);
reqdata.append(req);
System.out.println("请求报文:"+reqdata.toString());
output.write(reqdata.toString().getBytes());
output.flush();
socket.shutdownOutput();
InputStream input = socket.getInputStream();
System.out.println("响应报文:"+processIn(input));
}catch(Exception ex){
ex.printStackTrace();
}finally{
if(socket != null)
{
try {
socket.close();
} catch (IOException e) {
// TODO Auto-generated catch block
}
}
}
}
}

 

　 通过代码我们知道阻塞I/O是在调用InputStream.read()方法时是阻塞的，它会一直等到数据到来时(或超时)才会返回;同样，在调用ServerSocket.accept()方法时，也会一直阻塞到有客户端连接才会返回，每个客户端连接过来后，服务端都会启动一个线程去处理该客户端的请求。阻塞I/O的通信模型示意图如下：

　　如果你细细分析，一定会发现阻塞I/O存在一些缺点。根据阻塞I/O通信模型，我总结了它的两点缺点：

　　当客户端多时，会创建大量的处理线程。且每个线程都要占用栈空间和一些CPU时间

　　阻塞可能带来频繁的上下文切换，且大部分上下文切换可能是无意义的。

　　在这种情况下非阻塞式I/O就有了它的应用前景。