Example of TCP Stream Fragmenting

As mentioned in the function summary (in pseudo-code), in the section on reading and receiving, when reading or receiving a stream in a TCP application, you cannot know in advance how TCP will fragment the stream of data. Thus, what is sent in one write/send call, might need several read/recv calls. See there.

The code here shows an example. Here are the files:

• The client, or sender.
• The server, or receiver.
• The Makefile, to show you how to compile them. If you are not familiar with the 'make' command, you can type 'man make', or, better, read about 'make' via emacs' info mode.
• Here are other files that are needed to build these programs:
  • Code to convert strings to socket addresses, and vice-versa. Code to check for null strings and pointers.

Mr. Danzig can be reached at:
danzig@jct.ac.il.
Wyler Building, room 232, Sun-Thur 13:30 - 14:30
Telephone at work: 02-675-1218