I think you have a problem with your application code. Is your server in a loop which includes accept()?? Are U spawning a thread for every client request that you get? If it is multithreaded is your server waiting for all clients to end. As somebody else has suggested, check out the bible Unix Network Programming--W. Richard Stevens. If you wanna know about the gory implementation details of TCP, read TCP/IP Illustrated Vol 2 by the same author. Good luck! Hari ------------------------------------------------------------------------------ Hariharan L. Thantry thantryh@cse.msu.edu 4642, S. Hagadorn Road, #E6 Dept of Computer Science and Engg East Lansing, MI 48823 Michigan State University East Lansing, MI 48824-1226 Ph(res): 1-517-332-2645 Ph(off): 1-517-353-6646 ----------------------------------------------------------------------------- On Fri, 4 Aug 2000, Erik Verbruggen wrote: > > What I have seen from at the application layer is that > > all return response will ONLY be received until all > > requests have been sent. > > What network device are you using? Ethernet? If so, if it is not in > full-duplex mode and the server is continuously sending, the client > ethernet card just can't get onto the cable because the cable is used. > If you stop sending for a small amount of time, the client ethernet card > sees that the cable is unused and can send it's data. The other way is > to put the ethernet cards in full-duplex mode (not with coax and only > some cards can do this, and if you're using a hub, big chance the hub > does not support it). > > Erik. > - > : send the line "unsubscribe linux-net" in > the body of a message to majordomo@vger.rutgers.edu > - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu
