create new tag
, view all tags
The threaded file send program reads a specified file and sends it to the specified destination (excluding broadcasts, which are not allowed in file send). Frames are generated in the following order:
  • 1. The first frame contains the file name and the file size, separated by a newline character ‘/n’.
  • 2. The following frames contain the file contents.
  • 3. When EOF is reached, the final generated frame is blank to signify to the destination that there is no more data to write to the file.
As discussed above, generally, file transfer protocols require a means of reliable transmission. The lack of one here (due to the lack of an application layer acknowledgement) means that the file send program, after generating all the required frames, stays open until the user exits the program. It is therefore up to the user to ensure that all file send packets queued at the link layer are sent before terminating the testbed. Note that chat packets are of type TYPE_DATA and APP_FILE.

  • Figure 15: File send program landscape:
-- XiaohongWu - 2012-01-18
Topic revision: r2 - 2012-01-20 - XiaohongWu
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback