Compare the descriptor usage in a server using fork versus a server using a thread, assuming 100 clients are being serviced at the same time.


What happens in Figure if the thread does not close the connected socket when str_echo returns?


In Figures 5.5 and 6.13, we print "server terminated prematurely" when we expect an echoed line from the server but receive an EOF instead (recall Section 5.12). Modify Figure to print this message too, when appropriate.


Modify Figures 26.11 and 26.12 so that they can compile on a system that does not support threads.


To see the error with the readline function that is used in Figure, build that program and start the server. Then, build the TCP echo client from Figure that works in a batch mode correctly. Find a large text file on your system and start the client three times in a batch mode, reading from the large text file and writing its output to a temporary file. If possible, run the clients on a different host from the server. If the three clients terminate correctly (often they hang), look at their temporary output files and compare them to the input file.

Now build a version of the server using the correct readline function from Section 26.5. Rerun the test with three clients; all three clients should now work. You should also put a printf in the readline_destructor function, the readline_once function, and in the call to malloc in readline. This shows that the key is created only one time, but the memory is allocated for every thread, and that the destructor function is called for every thread.

     Python   SQL   Java   php   Perl 
     game development   web development   internet   *nix   graphics   hardware 
     telecommunications   C++ 
     Flash   Active Directory   Windows