3.6 Learning content, Androidwifip2p,golang http. Listenandserve operating mechanism,

This is a creation in Article, where the information may have evolved or changed.

Android Peer two articles:

http://blog.csdn.net/gophers/article/details/38060307

http://blog.csdn.net/max2005/article/details/12237905

Official Document: Http://developer.android.com/training/connect-devices-wirelessly/wifi-direct.html

Golang,

http://blog.csdn.net/gophers/article/details/37815009

2. Func (SRV *server) Serve (l net. Listener) Error {
4. Defer L.close ()
6.     var tempdelay time. duration   
8.     //  This cycle is the main cycle of the server, through the incoming listener receive requests from the client and establish a connection,   
10.     //  then creates routine for each connection to execute C.serve (), this c.serve is the specific service that handled   
12.     for  {  
14.         rw, e := l.accept ()   
16.         if  e != nil {   
18.             if  ne, ok := e. (NET. Error);  ok && ne. temporary ()  {  
20.                  if  tempdelay ==  0  {  
22.                      tempdelay = 5  * time. millisecond  
24.                  } else  {  
26.                      tempdelay *= 2   
28.                  }  
30.                  if  MAX :=  Span class= "number" style= "margin:0px; padding:0px; Border:none; Color:rgb (192,0,0); Background-color:inherit ">1  * time. second; tempdelay > max {  
32. Tempdelay = max
34. }
36.                  SRV.LOGF (" Http: accept error: %v; retrying in %v " , e, tempdelay)   
38.                  time. Sleep (Tempdelay)   
40.                  continue   
42.             }   
44.             return  E  
46.         }  
48.         tempdelay = 0   
50.         c, err := srv.newconn (rw)   
52.         if  err != nil {   
54.             continue   
56.         }  
58.         c.setstate (C.rwc, StateNew)    before serve can return   
60.         go c.serve ()  // <-here for each established connection to create a routine after the service &NBSP;&NBSP;
62. }
64. }

Line 30th means that the data returned by the thread is processed, so go generally has a lot of threads