Browse Prior Art Database

Method and Means of Handling File Replication Delays in an M/TFTP Transfer

IP.com Disclosure Number: IPCOM000012451D
Original Publication Date: 2003-May-07
Included in the Prior Art Database: 2003-May-07
Document File: 1 page(s) / 40K

Publishing Venue

IBM

Abstract

A method of hiding file replication delays within the MTFTP protocol is introduced.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 1

Method and Means of Handling File Replication Delays in an M/TFTP Transfer

       A hierarchical architecture is defined whereby a master data server is connected to multiple remote data servers, each of which is connected to multiple client systems. There exists a single master file repository on the master data server and a single local file repository on each of the remote data servers. The remote file repositories may contain a subset of the files in the master file repository...as the only files required at the remote d-server are those required by the clients connected to it. Files may be pushed from the master to the remote file repository. However to minimize the unnecessary transfer of files to remote d-servers where they will never be used (and to minimize required master server and system administrator knowledge), a pull mechanism is put into place. When a client attempts a unicast or multicast get of a file, the MTFTP Service on the remote d-server will check its local file repository to see if the file exists. If it does, the MTFTP transfer will continue according the standard MTFTP protocol. However, if the file does not exist, then the MTFTP service must replicate it. In this instance, depending on the size of the file and the bandwidth, the replication could take a long period of time. The problem to be solved is how to notify the client of this so that the client will not timeout waiting for the file and terminate execution. Ordinarily if a file was not...