CA2281672A1 - Process and apparatus for downloading data from a server computer to a client computer - Google Patents
Process and apparatus for downloading data from a server computer to a client computer Download PDFInfo
- Publication number
- CA2281672A1 CA2281672A1 CA002281672A CA2281672A CA2281672A1 CA 2281672 A1 CA2281672 A1 CA 2281672A1 CA 002281672 A CA002281672 A CA 002281672A CA 2281672 A CA2281672 A CA 2281672A CA 2281672 A1 CA2281672 A1 CA 2281672A1
- Authority
- CA
- Canada
- Prior art keywords
- data
- data file
- computer
- client
- download
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Abstract
A download of a data file from a server computer (10) to a client computer (12) is monitored by the client computer. The download is restarted automatically if a failure occurs. A failure may be a timeout, a loss of a connection, data errors, or other errors that terminate the download. The download may be restarted by instructing the server computer to start reading from a specified offset corresponding to an amount of data that was received reliably by the client, so that data is not unnecessarily retransmitted. This process increases the likelihood that a download will complete successfully.
The client program (20), if specialized for performing downloads, may be stored at the server. In response to a request to download a file, the client program is downloaded first, with the location of the requested file stored within the program. The client program is then executed on the client computer to transfer the requested file.
The client program (20), if specialized for performing downloads, may be stored at the server. In response to a request to download a file, the client program is downloaded first, with the location of the requested file stored within the program. The client program is then executed on the client computer to transfer the requested file.
Description
PROCESS AND APPARATUS FOR DOWNLOADING DATA
FROM A SERVER COMPUTER TO A CLIENT COMPUTER
Field of the Invention The present invention is related to processes and apparatus for transferring information between computers, particularly between a client computer and a server computer where the information is stored.
Background of the Invention In most computer networks it is desirable to have the capability to download, i.e., transfer, data from one computer to another. Typically, data is downloaded f ro m one computer on the network, such as an information provider's site on the Internet, to another site, i.e., computer, where the data is to be used. A file containing data, such as an executable program, graphics or other information, typically is made available for download a t one or more sites. The availability of the file i s advertised to potential users. Individuals who are interested in using the file access the site to download the file. This kind of information distribution reduces costs and enables efficient tracking of the use of the information.
There are several applications that provide a protocol for downloading files from a server computer to a client computer on a network. Example applications which use the Internet or other TCP/IP-based network include servers and clients that implement the hypertext transfer protocol (HTTP) and the file transfer protocol (FTP). A particular problem w i t h downloading information using applications that support these protocols is that the server application relies solely on the underlying transport protocol f o r reliability in the delivery of the data. If an error occurs during transmission of the data, the download simply terminates. For the download to complete successfully, the operation must be manually tried again, and the a n t i re file must be downloaded. Such a process can be t i m a consuming and frustrating, especially if the download is almost complete when a failure occurs.
However, the FTP specification, defined in Internet Request For Comments (RFC) 959, includes a restart procedure by which an interrupted FTP service command can be restarted from the point where it was interrupted.
This restart procedure is defined for only two of the three modes in which data transfer can occur: block mode and compressed mode. In block mode, d a t a i s transmitted as a series of data blocks preceded by one o r more header bytes. One of these header bytes includes descriptor codes, which may indicate a restart marker. I n compressed mode, transmitted data includes regular data, compressed data and an escape sequence o f two bytes. The escape sequence also includes descriptor codes that have the same meaning as in block mode.
To support restart in FTP, the sender of data must send data in block mode or compressed mode and insert a restart marker, or marker code, in the data stream w i t h some marker information. The marker information has meaning only to the sender, and could represent a b i t-count, a record-count, or any other information by which a system may identify a data checkpoint. The receiver o f data, if it implements the restart procedure, then marks the corresponding position of this marker in the receiving system. In the event of a failure, the user sends a command called RESTART, with a marker code as its argument. The sender then skips over the f i I a specified by the marker code to the data checkpoint specified by the marker code. The RESTART command must be immediately followed by whatever service command was interrupted, such as a read (RETR), w r i t a (STOR), directory (LIST) or append (APP). This restart procedure requires both the server to maintain a mapping between data checkpoints and marker codes for each operation and the client to monitor the marker codes received. Moreover, these commands are initiated manually by a user using the FTP client application.
Most currently available server and client programs that support FTP do not support block or compressed mode transfers, and generally support only a third mode o f transfer, called stream mode. Most browsers for the Internet also use only this mode of transfer for communication using HTTP. In stream mode, data i s transmitted as a stream of bytes, without restriction on the representation type used. If the structure of the data is a file structure, an end-of-file (EOF) indication i s indicated by the sending host closing the data connection and all bytes are data bytes. The FTP specification does not define any restart procedure for stream mode transfers. Accordingly, most currently available server and client programs that support FTP also do not support the RESTART command. If a failure occurs during a download, the operation must be manually tried again, and the entire file must be downloaded, obliging an individual to be present during the download.
Similarly, browsers using the HTTP protocol do not support any restart procedure. A proposed specification for a new version (1.1 ) of HTTP includes a range header i n a GET message to enable partial transfers and is intended to reduce unnecessary network usage. See Internet Request for Comments (RFC) 20fi8. However, the use of a partial GET command by the client is not specified. The HTTP 1.1 specification as proposed also states that a client should retry a request if a connection closes before any status, or a continue response, i s received from the server. However, there is no specification regarding error handling if data i s received from the server before a connection closes.
Apparently, if a failure occurs during a download, the operation must be manually tried again, and the entire file must be downloaded, obliging an individual to be present during the download. Accordingly, a general aim of this invention is to provide a download process and mechanism that simplifies the download process, and improves the likelihood of successful completion of the download. This functionality also allows the individual not to be present during the download.
Summary of the Invention In the present invention, a download is monitored by a client application and is restarted automatically if a failure occurs. Data read during the restarted download is appended to the existing file. Termination of a download might occur due to a failure of the server system or failure of the network or for many other reasons. These failures can be detected, for example, by monitoring whether valid data has been reliably received at the client within a specified period of t i m a .
Automatically restarting the download after such failures increases the likelihood of successful completion. I n a particular embodiment, the server application can transfer the data to the client as a stream of data w i t h little or no formatting or processing, for example by using the stream mode in I=fP. In this embodiment, the client monitors the amount of data reliably received. I n case of a failure, the client automatically sends another request to the server, instructing the server to start reading the file from a specified offset, determined by the amount of data already received. In this embodiment, there is no need for marker codes or other processing t o be performed and tracked by the server.
In another embodiment, the client program is specially adapted for performing only read or retrieve requests which reduces the size of its program code. In response to a request to download a file, the client program i s downloaded first from the server computer. The location of the requested file may be stored, or hard-coded, within the program. The client program is then executed on the client computer to transfer the requested file.
In another embodiment, the client program is used t o download files that are made available through other services, such as by a listing in a document published i n the hypertext markup language (HTML) via an HTTP server connected to a network. An HTML browser that accesses and displays the HTML file can display the files available for download as hypertext links. Selection of a hypertext link viewed in the browser causes the client program t o be executed to download the requested file. In t h i s embodiment, the client program may be resident at the client computer as a separate program, may be part of the browser or can be downloaded from the server before execution.
In these embodiments, the client program can be executed in response to some action by another program, at a time specified by the user or upon command from the user. By allowing a user to specify a time for a download operation in combination with the ability t o automatically restart a download, the user may be absent, yet have an increased likelihood that the download will be successful. The various embodiments can also be used in combination with each other.
Accordingly, one aspect of the present invention is a process or client system for downloading a data f i I a from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer. The process and client system have an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer. The client computer initiates a download of the data file by sending, using the application protocol, a request for the data file to the server computer over the computer network. Data received from the server computer as a stream of data in response to the request for the data file is monitored to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client. The amount of data successfully received by the client is stored when an error is detected that terminates the download. In response to a detected error that terminates the download of the data file, the download of the data file is automatically restarted by initiating a second download of the data file by sending, using the application protocol, a request for the data f i I a to the server computer, wherein the request specifies the amount of data successfully received.
In one embodiment, the download is initiated by sending a message to the server computer using a second application protocol requesting an indication of a port f o r a server process for performing the download. When indicator of the port is received, a message is sent to the server process using the application protocol at the indicated port to request the data file.
In another embodiment, the download is initiated by receiving from a user a specified time for performing the download of the data file. The message is sent to the server computer at the specified time.
Another aspect of the invention is a process and c I i a n t system for downloading a data file from a server computer to a client computer, wherein the data file i s stored on a computer readable medium connected to the server computer, wherein the process sends data over a computer network connecting the client computer t o the server computer. The client sends a request for a client program to the server computer over the computer network. The client program is receiving from the server computer, in response the request. The c I i a n t program when executed initiates a download of the data file by sending a request for the data file to the server computer over the computer network. The data received from the server computer in response to the request f o r the data file is monitored to detect termination of the download of the data file. In response to a detected error that terminates the download of the data f i I a , the download of the data file is automatically restarted by sending a request for the data file to the server computer.
In one embodiment, the download is monitored by tracking an amount of data from the data f i I a successfully received by the client. The amount of data successfully received is stored when an error is detected l0 that terminates the download. In this embodiment, the download of the data file may be automatically restarted by initiating a second download of the data f i I a by sending a request for the data file to the server computer, wherein the request specifies the amount o f data successfully received. This embodiment may be particularly useful where the application protocol sends data as a stream of data.
In another embodiment, the download is initiated by sending a message to the server computer requesting an indication of a port for a server process for performing the download. After the indicator of the port is received by the client a message is sent to the server process at the indicated port requesting the data file.
In another embodiment, the client program, when executed, receives from a user a specified time f o r performing the download of the data file. The message i s sent to the server computer at the specified time.
Another aspect of the present invention is a process o r server system for downloading a data file from a server computer to a client computer, wherein the data file i s stored on a computer readable medium connected to the server computer. The process uses an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer. A request is received for the data f i I a f r o m the client computer over the computer network, using the application protocol. Data is read from the data file and sent as a stream of data to the client computer using the application protocol. If the transfer terminates, after such a termination a request for the data file i s received from the client computer, wherein the request specifies the amount of data successfully received. The data is read from the data file starting from an offset determined according to the specified amount of data and is sent as a stream of data to the client computer using the application protocol.
Other aspects of the invention include a computer readable medium on which executable program logic i s stored, which when executed implements the c I i a n t system or the server system described above. Another aspect of the invention is a combination of the client system and the server system. Yet another aspect of the invention is the combined process performed by the combination of the client system and the server system.
In all aspects of the invention, the transport protocol may be TCP or other protocol. The network protocol may be, for example, the Internet protocol (IP), allowing the invention to be used on the fnternet or a private network.
The computer network may be an ethernet, an asynchronous transfer mode network, or any other kind of network.
By using a client that monitors a download and automatically restarting the download from the offset at which a failure occurs, the user does not need to be present to make sure a download is successful. By using a server which starts reading and sending data from a data file from a specified offset within the data file, an interrupted download may be restarted where it left off. The combination of this client and server system increase the likelihood of success of the download and eliminate unnecessary data transfer.
In yet another preferred embodiment, a smart peripheral or computing system, a proxy computing system, in close communications with a client computer, may be designated to handle all the data files and other transfers between the client and the server over a communications network. The proxy has the advantage of off loading the task of the client computer while handling the transfers to and from a server most efficiently. The proxy system can be controlled and configured by the client computer to handle all the transfers over the communication network to and from a server computing system in the various arrangements described above and below of monitored downloading and automatic resumption of the downloading from whenever a transfer may have been interrupted. The client computer to proxy interface may be set up such that the proxy contains all the necessary resources as attributed to the client computing systems as described herein. In this manner the proxy accomplishes the transfers to and from the server while only informing the client computer when such transfers are completed. Such control and interfacing between the client and the proxy are well known in the art.
An advantage of using a proxy system is that the proxy system may be designed specifically for and dedicated to these client/server transfers. In this instance the hardware/software for the proxy can be adapted for this one task making the proxy most efficient.
Other objects, features and advantages will be apparent from the following detailed description o f preferred embodiments thereof taken in conjunction w i t h the accompanying drawings.
Brief Description of the Drawings In the drawings, Fig. 1 is a block diagram illustrating a server computer and a client computer which improves the likelihood of a successful download of information;
Fig. 2 is a block diagram of a typical general purpose computer system which may be used to implement a client computer or a server computer in Fig. 1;
Fig. 3 is an illustration of a typical memory system shown in Fig. 2;
Fig. 4 is a block diagram of one embodiment of the present invention wherein a server sends a client the client program;
Fig. 5 is a flow chart illustrating how the client computer monitors a download in one embodiment of the invention;
Fig. 6 is a flow chart illustrating how the client computer determines whether a download operation i s incomplete in one embodiment of the invention; and Fig. 7 is a flow chart illustrating how the server computer processes of a request for a portion of a data file in one embodiment of the invention.
Detailed Description of Preferred Embodiments The present invention will be more completely understood through the following detailed description which should be read in conjunction with the attached drawing in which similar reference numbers indicate similar structures.
Referring now to Fig. 1, the present invention i s related to improving the likelihood of success o f downloads of data from a server computer 10 to a c 1 i a n t computer 12 over a network 14. The network 14, f o r example, may be an ethernet network, an asynchronous transfer mode network or other kind of network. The network protocol, for example, may be the Internet protocol (IP). The transport protocol may be, f o r example, the user datagram protocol (UDP), the transport control protocol (TCP) or other protocol. The use o f TCP/IP is described in Internetworking with TCP/IP, Vols. I and II, by D.E. Comer and D.L Stevens, Prentice-Hall, inc., 1991. TCP/IP is particularly useful because i t is both reliable and available for most networking technology.
The server computer 10 has a file transfer server 1 6 which can be accessed by an executed client program 1 8 over the network 14. Several client programs 18 are available, such as browsers for the World Wide Web which may download files or read and display HTML documents, such as the Navigator browser from Netscape Communications, Inc., or the Internet Explorer browser, from Microsoft Corporation, or FTP clients such as the "WS_FTP" I=TP client available from Ipswitch, Inc.
The file transfer server 16 makes various information available, such as data files stored on a storage device 20 which are accessed through the file system o f the server computer 10. On the Internet, such f i I a transfer servers include HTTP servers and FTP servers.
Such file transfer server, in response to requests from a client computer, open and read a data file and use the TCP/IP protocol to establish a connection with the client, then transfer data from a data file to the client.
However, these file transfer servers typically do not ensure that the client reliably receives the requested data and rely on the TCP/IP protocol to provide reliable data transfer.
In one embodiment of the present invention, the f i I a transfer server is a computer program executed on the server computer which uses read and send commands available through the operating system on the server computer to access the file system and the transport protocol of the network. These commands allow an application to read data files from the storage device 20 and send data over the network 14, for example by using TCP as the transport protocol and IP as the network protocol. If the server computer is supported by the UNIX
operating system, the "read" and "send" commands available through the UNIX operating system can be used in a computer program, for example, implemented in the "C" programming language.
The executed client program 18 establishes a connection with the file transfer server, e.g., and requests a data file using commands in an application protocol supported by the file transfer server. The executed client program also includes a process f o r monitoring the download operation as indicated at 22.
This process monitors the data as it is received and w h i I a it is stored on the storage medium 24. If the download i s interrupted for some reason, for example an error occurs in initiating the download operation, the request for data is repeated. 1n particular, if the underlying transport and network protocols, such as TCP/IP, cause the server computer to terminate the download process, the executed client program can detect this condition, for example by using a time out operation. The download operation can then be restarted by another request. In a particular embodiment of the invention, the server includes a module 26 which is capable of processing requests for reading data from a file starting from a specified offset. fn this embodiment, the client keeps track of how much data has been reliably received and requests the server to retrieve the remainder of the data file starting from a specified offset, thus avoiding the need to retransmit the entire data file.
In one embodiment of the invention, the client program is stored at the server. In response to a request t o download a file, using a different application protocol between a different file transfer server and a different client, the client program is downloaded first, w i t h the location of the requested file stored within the program. The client program is then executed on the client computer to transfer the requested file. This embodiment of the invention is particularly useful f o r downloading files that are made available through other services, such as by a listing in a document published i n the hypertext markup language (HTML) via an HTTP server connected to a computer network. A browser that accesses and displays the HTML file can display f i I a s available for download as hypertext links. Selection of a hypertext link viewed in the browser may cause the client program to be downloaded, which then downloads the requested file. The client program can be made sufficiently small, specifically as it downloads, so that downloading of the client program takes little time.
Alternatively, the client program may be resident at the client computer. The client program can be executed immediately, at a time specified by the user or upon command from the user or an application.
A suitable computer system to implement either the server computer 10 or client computer 12 is shown i n Fig. 2 and typically includes an output device 36 which displays information to a user. The computer system includes a main unit 28 connected to the output device and an input device 38, such as a keyboard or mouse. The main unit generally includes a processor 30 connected t o a memory system 34 via an interconnection mechanism 32. The input device 38 is also connected to the processor and memory system via the interconnection mechanism 32, as is the output device 36.
It should be understood that one or more output devices may be connected to the computer system.
Example output devices include a cathode ray tube (CRT) display, liquid crystal displays (LCD), printers, communication devices such as a modem, and audio output. It should also be understood that one or more input devices may be connected to the computer system.
Example input devices include a keyboard, keypad, track ball, mouse, pen and tablet, communication device, audio input and scanner. It should be understood the invention is not limited to the particular input or output devices used in combination with the computer system o r t o those described herein.
The computer system 20 may be a general purpose computer system which is programmable using a high level computer programming language, such as "C,"
"C++" "Pascal," "Visual Basic" or other language. The computer system may also be specially programmed, special purpose hardware. In a general purpose computer system, the processor is typically a commercially available processor, of which the series x86 processors, including a Pentium processor using MMX extensions available from Intel, and the 680X0 series microprocessors available from Motorola are examples. Many other processors are available. Such a microprocessor executes a program called an operating system, of which Windows95, WindowsNT, UNIX, DOS and VMS are examples, which controls the execution o f other computer programs and provides scheduling, debugging, input/output control, accounting, compilation, storage assignment in a file system containing named files of data, data management and memory management, communication control, protection and related services.
The processor and operating system define a computer platform for which application programs in high-level programming languages are written.
A memory system shown in more detail in Fig. 3, typically includes a computer readable and writeable nonvolatile recording medium 42, of which a magnetic disk, a flash memory and tape are examples. The d i s k may be removable, known as a floppy disk, or permanent, known as a hard drive. A disk has a number of tracks 4 4 in which signals are stored, typically in binary form, i.e., a form interpreted as a sequence of one and zeros as shown 46 and 48. Such signals may define, for example, an application program to be executed by the microprocessor, or information stored on the disk to be processed by the application program. Typically, in operation, the processor causes data to be read from the nonvolatile recording medium 42 into an integrated circuit memory element 40, which is typically a volatile, random access memory such as a dynamic random access memory (DRAM) or static memory (SRAM). The integrated circuit memory element allows for faster access to the information by the processor than does the disk. The processor generally manipulates the data within the integrated circuit memory and copies the data to and from the disk if the data is not being used. A variety o f mechanisms are known for managing data movement between the disk and the integrated circuit memory element, and the invention is not limited thereto. ! t should also be understood that the invention is n of limited to a particular memory system.
It should be understood the invention is not limited t o a particular computer platform, particular processor, or particular high-level programming language.
Additionally, the computer system may be a multiprocessor computer system or may include multiple computers connected over a computer network.
With reference to FIGS. 1-4, in another preferred embodiment the client computer 12 is a dedicated computer or central processing unit (CPU) or specially designed processing system for performing the transfers to and from a server over a communications network. I n this instance the client 12 is a proxy of the actual c I i a n t with which the user interfaces. In this case the proxy may be housed in the client computer, it may share common memory with the client, and/or it may be connected to the client computer on any of the available suitable I/O ports, e.g and SCSI, parallel, or serial. It i s possible that the proxy is implemented as an ASIC
(application specific integrated circuit) mounted w i t h i n the actual client computer. In other cases, the proxy may be connected to the client via a wireless connection. The proxy may have on-board programming, or the proxy programming may be loaded from the actual client by w a I I
known methods. However, when loaded and executed, the proxy program will ~ accomplish the monitored data transfers as described for the client computers of the other preferred embodiments herein. In a preferred embodiment, the proxy may share common main memory with the actual client computer, wherein interrupts o r flags may be used for communication between the proxy and the actual client. fn other well known implementations where the proxy is a smart peripheral, or a smart modem peripheral to the actual c I i a n t computer, well known techniques of handshaking, flags, and interrupts may be used. Such systems may be designed with flexibility as known in the art. For example, a s m a rt peripheral may be arranged to accomplish some transfers under a priority basis while other transfers may be accomplished during low activity periods. Such control o f the timing of transfers by proxy are well known.
In one embodiment of the present invention, the c I i a n t program may. be implemented as a computer program, f o r example in the "C++" programming language and compiled for execution on the desired platform, such as a machine with a Windows95 operating system. The program also may be implemented, for example, in the Java programming language, where a browser would execute the Java program to download the requested file. I n general, this program, when executed, has the capability of transferring files from a server computer over a network using an application protocol to communicate with the file transfer server. This client program may be implemented by using at least the read commands available in FTP. The client program has, in addition, the capability to monitor a download operation while i t occurs and to automatically restart or continue the download from the point where an interrupt occurs. i n one embodiment, a user may specify a time at which the program will be executed to initiate the download. A
user may also specify alternative parameters for a download, such as a connection location or another copy of the file to be downloaded.
On the server computer, the file transfer server also may be implemented as a computer program, for example, in the "C" programming language, and compiled f o r execution on the desired platform, such a machine with a UNIX or WindowsNT operating system. In general, this program, when executed, has the capability o f handling client requests to transfer files over a network.
Using the same application protocol defined with the client program. For example, the file transfer server may be implemented as an FTP server. In addition, the file transfer server has the capability of opening, reading and transmitting data starting from a specified offset i n a data file, where the offset is parameter received fro m a client, typically as a part of a request from t h a c I i a n t to read a particular data file.
One embodiment of the invention will now be described in connection with Fig. 4. in this embodiment, the f i I a transfer server is referred to as a download server 122 which is separate from a standard FTP server 120 operating on the same machine. Because the download server would not be assigned a well-known port according to Internet standards, a client program would need to locate the download server.
The server computer includes the FTP server 120 that communicates using ports 126, which are port numbers 20 and 21 according to convention for the Internet. The download server 122 also is provided on a port 124 which could be any of a number of ports available on the server computer. It is possible that this port could vary fro m one server computer to another server computer.
Accordingly, the indication of the port number "x" i s stored in a file at the time the download server i s instantiated or executed on the machine, after it has been assigned a port number. This file is preferably stored i n the same location with respect to an FTP server on the same machine, and thus will have a predetermined name and path, e.g., "download/port_file." The absence o f this file should indicate that the download server i s unavailable.
When the client computer executes the client program, the executed client program 18 communicates with the FTP server 120 to retrieve the port file as indicated a t 128. This port file is returned in step 142 to the client as indicated in 130. The client reads the port file t o obtain the port number for the download server 122. The client can then communicate with the download server via messages sent to port "x."
One embodiment of the process performed by the execute client program 18, and particularly module 22, for initiating and monitoring a download will now be described in more detail connection with Figs. 5 and 6.
This process may begin when the client program is executed or at a specified time. For example, if the client program is downloaded with Internet Explorer browser, this browser requests input from the user t o indicate whether the file should be opened (executed) o r saved. If the file is saved, it can be executed at a later time.
When executed, the client program may request a user to specify a time for the download to occur, using any appropriate user interface, or a time may be automatically specified. When the download begins, a variable value, indicative of the total bytes received, i s initialized to zero in step 50. This number will be used to determine how much of a data file has been received, in case a failure occurs during the download process.
Next, if necessary, the client connects to the Internet i n step 52. The connection may be initiated by an automatic dial-up connection to an Internet service provider and/or by assignment of an IP address to the client, if necessary, or by any other means. A test for an existing connection also can be made. If a failure occurs, as tested for i n step 54, a connection attempt in step 52 may be performed again. An alternate connection also may be attempted. Otherwise, the client initiates an FTP
transfer to retrieve the file indicating the port number of the download server by sending a message to the FTP
server including a user name and password, if necessary, in step 56. This message establishes a connection between the FTP server and the executed client program.
User names and passwords commonly are used when the FTP protocol is used to download files. If a fai I a re occurs, as determined in step 58, the process may be restarted, for example by returning to step 56 or step 52, depending on the type of error. It is possible t o implement the system so that it waits, in step 60, i n order to allow time before resending a message, f o r example to allow time for a system failure to be remedied.
If the user name and password are successfully sent i n step 56, the type of transfer to be performed is then sent to the FTP server in step 62. This is another form of FTP
message. If this step is successfully completed, the client's port is then sent to the server in step 66, t o inform the FTP server which port on the client machine will receive the data. If this command i s completed successfully, a command to retrieve the f i I a containing the port number of the download server is sent to the FTP server in step 68. The client program may specify the file, for example, by using a uniform resource locator (URL). A URL is defined by an Internet Request For Comments (RFC) document. It includes an indicator of a protocol (e.g., ftp or http or other protocol), a site (e.g., ethos.com), and a path (e.g., "a/b/c/filename.txt") for a specific file. It also may include a delimiter, e.g., "?," after which parameters may be added. A URL thus may look like the following:
ftp://ethos.com/a/b/c/filename.txt?parameter.
If either step 62 or 66 fails, as determined in step 64 and 67, respectively, the process can be restarted, possibly including the wait step 60, and returning t o either step 52 or 56 depending on the type of error.
After the client sends the retrieve file command, the FTP
server transmits the port file to the specified port at the client. The client then reads and stores the data. I f this read is not successful, retries are performed. I t should also be indicated that, as illustrated at 72, that the number of retries may be limited by number or by time. If the read operations are reliably completed, the client then in step 74 proceeds to transfer the desired file from the download server by sending read requests to the port designated in the port file, as described in more detail below in connection with Fig. 6.
Referring now to Fig. 6, one embodiment of the process of transferring data to the client from the download server will now be described. First, the client establishes in step 76 a connection with the download server in a manner similar to how a connection i s established with the FTP server. If an error occurs, the error can be reported to the user or an alternate connection may be tried. A filename for a data file f o r receiving the downloaded file is specified in step 77.
This may be done through any appropriate user interface.
If the file does not exist, as determined in step 78, it i s created an opened in write mode in step 79, otherwise i t is opened in append mode in step 80. The client then sends a read request to the download server, and a specified offset, in step 81. Processing by the download server to send the data is described in more detail below in connection with Fig. 7.
Data received at the client is read from a socket (a construct in the TCP/IP protocol) at the indicated port i n step 82, for example, using the "recv()" command. If the data read from the socket indicates that valid data is not available, as determined in step 84, e.g., by returning " -1," the socket is continually read by returning to step 82, subject to a time out operation as determined in step 92.
If a time out occurs, the file on the client is closed, and the process of downloading automatically restarts w i t h step 76, of reestablishing the connection w i t h the download server. The automatic restarts from step 76 also may be limited, in number or in time, allowing automatic restart, for example, from step 52 or 56 of Fig.
FROM A SERVER COMPUTER TO A CLIENT COMPUTER
Field of the Invention The present invention is related to processes and apparatus for transferring information between computers, particularly between a client computer and a server computer where the information is stored.
Background of the Invention In most computer networks it is desirable to have the capability to download, i.e., transfer, data from one computer to another. Typically, data is downloaded f ro m one computer on the network, such as an information provider's site on the Internet, to another site, i.e., computer, where the data is to be used. A file containing data, such as an executable program, graphics or other information, typically is made available for download a t one or more sites. The availability of the file i s advertised to potential users. Individuals who are interested in using the file access the site to download the file. This kind of information distribution reduces costs and enables efficient tracking of the use of the information.
There are several applications that provide a protocol for downloading files from a server computer to a client computer on a network. Example applications which use the Internet or other TCP/IP-based network include servers and clients that implement the hypertext transfer protocol (HTTP) and the file transfer protocol (FTP). A particular problem w i t h downloading information using applications that support these protocols is that the server application relies solely on the underlying transport protocol f o r reliability in the delivery of the data. If an error occurs during transmission of the data, the download simply terminates. For the download to complete successfully, the operation must be manually tried again, and the a n t i re file must be downloaded. Such a process can be t i m a consuming and frustrating, especially if the download is almost complete when a failure occurs.
However, the FTP specification, defined in Internet Request For Comments (RFC) 959, includes a restart procedure by which an interrupted FTP service command can be restarted from the point where it was interrupted.
This restart procedure is defined for only two of the three modes in which data transfer can occur: block mode and compressed mode. In block mode, d a t a i s transmitted as a series of data blocks preceded by one o r more header bytes. One of these header bytes includes descriptor codes, which may indicate a restart marker. I n compressed mode, transmitted data includes regular data, compressed data and an escape sequence o f two bytes. The escape sequence also includes descriptor codes that have the same meaning as in block mode.
To support restart in FTP, the sender of data must send data in block mode or compressed mode and insert a restart marker, or marker code, in the data stream w i t h some marker information. The marker information has meaning only to the sender, and could represent a b i t-count, a record-count, or any other information by which a system may identify a data checkpoint. The receiver o f data, if it implements the restart procedure, then marks the corresponding position of this marker in the receiving system. In the event of a failure, the user sends a command called RESTART, with a marker code as its argument. The sender then skips over the f i I a specified by the marker code to the data checkpoint specified by the marker code. The RESTART command must be immediately followed by whatever service command was interrupted, such as a read (RETR), w r i t a (STOR), directory (LIST) or append (APP). This restart procedure requires both the server to maintain a mapping between data checkpoints and marker codes for each operation and the client to monitor the marker codes received. Moreover, these commands are initiated manually by a user using the FTP client application.
Most currently available server and client programs that support FTP do not support block or compressed mode transfers, and generally support only a third mode o f transfer, called stream mode. Most browsers for the Internet also use only this mode of transfer for communication using HTTP. In stream mode, data i s transmitted as a stream of bytes, without restriction on the representation type used. If the structure of the data is a file structure, an end-of-file (EOF) indication i s indicated by the sending host closing the data connection and all bytes are data bytes. The FTP specification does not define any restart procedure for stream mode transfers. Accordingly, most currently available server and client programs that support FTP also do not support the RESTART command. If a failure occurs during a download, the operation must be manually tried again, and the entire file must be downloaded, obliging an individual to be present during the download.
Similarly, browsers using the HTTP protocol do not support any restart procedure. A proposed specification for a new version (1.1 ) of HTTP includes a range header i n a GET message to enable partial transfers and is intended to reduce unnecessary network usage. See Internet Request for Comments (RFC) 20fi8. However, the use of a partial GET command by the client is not specified. The HTTP 1.1 specification as proposed also states that a client should retry a request if a connection closes before any status, or a continue response, i s received from the server. However, there is no specification regarding error handling if data i s received from the server before a connection closes.
Apparently, if a failure occurs during a download, the operation must be manually tried again, and the entire file must be downloaded, obliging an individual to be present during the download. Accordingly, a general aim of this invention is to provide a download process and mechanism that simplifies the download process, and improves the likelihood of successful completion of the download. This functionality also allows the individual not to be present during the download.
Summary of the Invention In the present invention, a download is monitored by a client application and is restarted automatically if a failure occurs. Data read during the restarted download is appended to the existing file. Termination of a download might occur due to a failure of the server system or failure of the network or for many other reasons. These failures can be detected, for example, by monitoring whether valid data has been reliably received at the client within a specified period of t i m a .
Automatically restarting the download after such failures increases the likelihood of successful completion. I n a particular embodiment, the server application can transfer the data to the client as a stream of data w i t h little or no formatting or processing, for example by using the stream mode in I=fP. In this embodiment, the client monitors the amount of data reliably received. I n case of a failure, the client automatically sends another request to the server, instructing the server to start reading the file from a specified offset, determined by the amount of data already received. In this embodiment, there is no need for marker codes or other processing t o be performed and tracked by the server.
In another embodiment, the client program is specially adapted for performing only read or retrieve requests which reduces the size of its program code. In response to a request to download a file, the client program i s downloaded first from the server computer. The location of the requested file may be stored, or hard-coded, within the program. The client program is then executed on the client computer to transfer the requested file.
In another embodiment, the client program is used t o download files that are made available through other services, such as by a listing in a document published i n the hypertext markup language (HTML) via an HTTP server connected to a network. An HTML browser that accesses and displays the HTML file can display the files available for download as hypertext links. Selection of a hypertext link viewed in the browser causes the client program t o be executed to download the requested file. In t h i s embodiment, the client program may be resident at the client computer as a separate program, may be part of the browser or can be downloaded from the server before execution.
In these embodiments, the client program can be executed in response to some action by another program, at a time specified by the user or upon command from the user. By allowing a user to specify a time for a download operation in combination with the ability t o automatically restart a download, the user may be absent, yet have an increased likelihood that the download will be successful. The various embodiments can also be used in combination with each other.
Accordingly, one aspect of the present invention is a process or client system for downloading a data f i I a from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer. The process and client system have an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer. The client computer initiates a download of the data file by sending, using the application protocol, a request for the data file to the server computer over the computer network. Data received from the server computer as a stream of data in response to the request for the data file is monitored to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client. The amount of data successfully received by the client is stored when an error is detected that terminates the download. In response to a detected error that terminates the download of the data file, the download of the data file is automatically restarted by initiating a second download of the data file by sending, using the application protocol, a request for the data f i I a to the server computer, wherein the request specifies the amount of data successfully received.
In one embodiment, the download is initiated by sending a message to the server computer using a second application protocol requesting an indication of a port f o r a server process for performing the download. When indicator of the port is received, a message is sent to the server process using the application protocol at the indicated port to request the data file.
In another embodiment, the download is initiated by receiving from a user a specified time for performing the download of the data file. The message is sent to the server computer at the specified time.
Another aspect of the invention is a process and c I i a n t system for downloading a data file from a server computer to a client computer, wherein the data file i s stored on a computer readable medium connected to the server computer, wherein the process sends data over a computer network connecting the client computer t o the server computer. The client sends a request for a client program to the server computer over the computer network. The client program is receiving from the server computer, in response the request. The c I i a n t program when executed initiates a download of the data file by sending a request for the data file to the server computer over the computer network. The data received from the server computer in response to the request f o r the data file is monitored to detect termination of the download of the data file. In response to a detected error that terminates the download of the data f i I a , the download of the data file is automatically restarted by sending a request for the data file to the server computer.
In one embodiment, the download is monitored by tracking an amount of data from the data f i I a successfully received by the client. The amount of data successfully received is stored when an error is detected l0 that terminates the download. In this embodiment, the download of the data file may be automatically restarted by initiating a second download of the data f i I a by sending a request for the data file to the server computer, wherein the request specifies the amount o f data successfully received. This embodiment may be particularly useful where the application protocol sends data as a stream of data.
In another embodiment, the download is initiated by sending a message to the server computer requesting an indication of a port for a server process for performing the download. After the indicator of the port is received by the client a message is sent to the server process at the indicated port requesting the data file.
In another embodiment, the client program, when executed, receives from a user a specified time f o r performing the download of the data file. The message i s sent to the server computer at the specified time.
Another aspect of the present invention is a process o r server system for downloading a data file from a server computer to a client computer, wherein the data file i s stored on a computer readable medium connected to the server computer. The process uses an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer. A request is received for the data f i I a f r o m the client computer over the computer network, using the application protocol. Data is read from the data file and sent as a stream of data to the client computer using the application protocol. If the transfer terminates, after such a termination a request for the data file i s received from the client computer, wherein the request specifies the amount of data successfully received. The data is read from the data file starting from an offset determined according to the specified amount of data and is sent as a stream of data to the client computer using the application protocol.
Other aspects of the invention include a computer readable medium on which executable program logic i s stored, which when executed implements the c I i a n t system or the server system described above. Another aspect of the invention is a combination of the client system and the server system. Yet another aspect of the invention is the combined process performed by the combination of the client system and the server system.
In all aspects of the invention, the transport protocol may be TCP or other protocol. The network protocol may be, for example, the Internet protocol (IP), allowing the invention to be used on the fnternet or a private network.
The computer network may be an ethernet, an asynchronous transfer mode network, or any other kind of network.
By using a client that monitors a download and automatically restarting the download from the offset at which a failure occurs, the user does not need to be present to make sure a download is successful. By using a server which starts reading and sending data from a data file from a specified offset within the data file, an interrupted download may be restarted where it left off. The combination of this client and server system increase the likelihood of success of the download and eliminate unnecessary data transfer.
In yet another preferred embodiment, a smart peripheral or computing system, a proxy computing system, in close communications with a client computer, may be designated to handle all the data files and other transfers between the client and the server over a communications network. The proxy has the advantage of off loading the task of the client computer while handling the transfers to and from a server most efficiently. The proxy system can be controlled and configured by the client computer to handle all the transfers over the communication network to and from a server computing system in the various arrangements described above and below of monitored downloading and automatic resumption of the downloading from whenever a transfer may have been interrupted. The client computer to proxy interface may be set up such that the proxy contains all the necessary resources as attributed to the client computing systems as described herein. In this manner the proxy accomplishes the transfers to and from the server while only informing the client computer when such transfers are completed. Such control and interfacing between the client and the proxy are well known in the art.
An advantage of using a proxy system is that the proxy system may be designed specifically for and dedicated to these client/server transfers. In this instance the hardware/software for the proxy can be adapted for this one task making the proxy most efficient.
Other objects, features and advantages will be apparent from the following detailed description o f preferred embodiments thereof taken in conjunction w i t h the accompanying drawings.
Brief Description of the Drawings In the drawings, Fig. 1 is a block diagram illustrating a server computer and a client computer which improves the likelihood of a successful download of information;
Fig. 2 is a block diagram of a typical general purpose computer system which may be used to implement a client computer or a server computer in Fig. 1;
Fig. 3 is an illustration of a typical memory system shown in Fig. 2;
Fig. 4 is a block diagram of one embodiment of the present invention wherein a server sends a client the client program;
Fig. 5 is a flow chart illustrating how the client computer monitors a download in one embodiment of the invention;
Fig. 6 is a flow chart illustrating how the client computer determines whether a download operation i s incomplete in one embodiment of the invention; and Fig. 7 is a flow chart illustrating how the server computer processes of a request for a portion of a data file in one embodiment of the invention.
Detailed Description of Preferred Embodiments The present invention will be more completely understood through the following detailed description which should be read in conjunction with the attached drawing in which similar reference numbers indicate similar structures.
Referring now to Fig. 1, the present invention i s related to improving the likelihood of success o f downloads of data from a server computer 10 to a c 1 i a n t computer 12 over a network 14. The network 14, f o r example, may be an ethernet network, an asynchronous transfer mode network or other kind of network. The network protocol, for example, may be the Internet protocol (IP). The transport protocol may be, f o r example, the user datagram protocol (UDP), the transport control protocol (TCP) or other protocol. The use o f TCP/IP is described in Internetworking with TCP/IP, Vols. I and II, by D.E. Comer and D.L Stevens, Prentice-Hall, inc., 1991. TCP/IP is particularly useful because i t is both reliable and available for most networking technology.
The server computer 10 has a file transfer server 1 6 which can be accessed by an executed client program 1 8 over the network 14. Several client programs 18 are available, such as browsers for the World Wide Web which may download files or read and display HTML documents, such as the Navigator browser from Netscape Communications, Inc., or the Internet Explorer browser, from Microsoft Corporation, or FTP clients such as the "WS_FTP" I=TP client available from Ipswitch, Inc.
The file transfer server 16 makes various information available, such as data files stored on a storage device 20 which are accessed through the file system o f the server computer 10. On the Internet, such f i I a transfer servers include HTTP servers and FTP servers.
Such file transfer server, in response to requests from a client computer, open and read a data file and use the TCP/IP protocol to establish a connection with the client, then transfer data from a data file to the client.
However, these file transfer servers typically do not ensure that the client reliably receives the requested data and rely on the TCP/IP protocol to provide reliable data transfer.
In one embodiment of the present invention, the f i I a transfer server is a computer program executed on the server computer which uses read and send commands available through the operating system on the server computer to access the file system and the transport protocol of the network. These commands allow an application to read data files from the storage device 20 and send data over the network 14, for example by using TCP as the transport protocol and IP as the network protocol. If the server computer is supported by the UNIX
operating system, the "read" and "send" commands available through the UNIX operating system can be used in a computer program, for example, implemented in the "C" programming language.
The executed client program 18 establishes a connection with the file transfer server, e.g., and requests a data file using commands in an application protocol supported by the file transfer server. The executed client program also includes a process f o r monitoring the download operation as indicated at 22.
This process monitors the data as it is received and w h i I a it is stored on the storage medium 24. If the download i s interrupted for some reason, for example an error occurs in initiating the download operation, the request for data is repeated. 1n particular, if the underlying transport and network protocols, such as TCP/IP, cause the server computer to terminate the download process, the executed client program can detect this condition, for example by using a time out operation. The download operation can then be restarted by another request. In a particular embodiment of the invention, the server includes a module 26 which is capable of processing requests for reading data from a file starting from a specified offset. fn this embodiment, the client keeps track of how much data has been reliably received and requests the server to retrieve the remainder of the data file starting from a specified offset, thus avoiding the need to retransmit the entire data file.
In one embodiment of the invention, the client program is stored at the server. In response to a request t o download a file, using a different application protocol between a different file transfer server and a different client, the client program is downloaded first, w i t h the location of the requested file stored within the program. The client program is then executed on the client computer to transfer the requested file. This embodiment of the invention is particularly useful f o r downloading files that are made available through other services, such as by a listing in a document published i n the hypertext markup language (HTML) via an HTTP server connected to a computer network. A browser that accesses and displays the HTML file can display f i I a s available for download as hypertext links. Selection of a hypertext link viewed in the browser may cause the client program to be downloaded, which then downloads the requested file. The client program can be made sufficiently small, specifically as it downloads, so that downloading of the client program takes little time.
Alternatively, the client program may be resident at the client computer. The client program can be executed immediately, at a time specified by the user or upon command from the user or an application.
A suitable computer system to implement either the server computer 10 or client computer 12 is shown i n Fig. 2 and typically includes an output device 36 which displays information to a user. The computer system includes a main unit 28 connected to the output device and an input device 38, such as a keyboard or mouse. The main unit generally includes a processor 30 connected t o a memory system 34 via an interconnection mechanism 32. The input device 38 is also connected to the processor and memory system via the interconnection mechanism 32, as is the output device 36.
It should be understood that one or more output devices may be connected to the computer system.
Example output devices include a cathode ray tube (CRT) display, liquid crystal displays (LCD), printers, communication devices such as a modem, and audio output. It should also be understood that one or more input devices may be connected to the computer system.
Example input devices include a keyboard, keypad, track ball, mouse, pen and tablet, communication device, audio input and scanner. It should be understood the invention is not limited to the particular input or output devices used in combination with the computer system o r t o those described herein.
The computer system 20 may be a general purpose computer system which is programmable using a high level computer programming language, such as "C,"
"C++" "Pascal," "Visual Basic" or other language. The computer system may also be specially programmed, special purpose hardware. In a general purpose computer system, the processor is typically a commercially available processor, of which the series x86 processors, including a Pentium processor using MMX extensions available from Intel, and the 680X0 series microprocessors available from Motorola are examples. Many other processors are available. Such a microprocessor executes a program called an operating system, of which Windows95, WindowsNT, UNIX, DOS and VMS are examples, which controls the execution o f other computer programs and provides scheduling, debugging, input/output control, accounting, compilation, storage assignment in a file system containing named files of data, data management and memory management, communication control, protection and related services.
The processor and operating system define a computer platform for which application programs in high-level programming languages are written.
A memory system shown in more detail in Fig. 3, typically includes a computer readable and writeable nonvolatile recording medium 42, of which a magnetic disk, a flash memory and tape are examples. The d i s k may be removable, known as a floppy disk, or permanent, known as a hard drive. A disk has a number of tracks 4 4 in which signals are stored, typically in binary form, i.e., a form interpreted as a sequence of one and zeros as shown 46 and 48. Such signals may define, for example, an application program to be executed by the microprocessor, or information stored on the disk to be processed by the application program. Typically, in operation, the processor causes data to be read from the nonvolatile recording medium 42 into an integrated circuit memory element 40, which is typically a volatile, random access memory such as a dynamic random access memory (DRAM) or static memory (SRAM). The integrated circuit memory element allows for faster access to the information by the processor than does the disk. The processor generally manipulates the data within the integrated circuit memory and copies the data to and from the disk if the data is not being used. A variety o f mechanisms are known for managing data movement between the disk and the integrated circuit memory element, and the invention is not limited thereto. ! t should also be understood that the invention is n of limited to a particular memory system.
It should be understood the invention is not limited t o a particular computer platform, particular processor, or particular high-level programming language.
Additionally, the computer system may be a multiprocessor computer system or may include multiple computers connected over a computer network.
With reference to FIGS. 1-4, in another preferred embodiment the client computer 12 is a dedicated computer or central processing unit (CPU) or specially designed processing system for performing the transfers to and from a server over a communications network. I n this instance the client 12 is a proxy of the actual c I i a n t with which the user interfaces. In this case the proxy may be housed in the client computer, it may share common memory with the client, and/or it may be connected to the client computer on any of the available suitable I/O ports, e.g and SCSI, parallel, or serial. It i s possible that the proxy is implemented as an ASIC
(application specific integrated circuit) mounted w i t h i n the actual client computer. In other cases, the proxy may be connected to the client via a wireless connection. The proxy may have on-board programming, or the proxy programming may be loaded from the actual client by w a I I
known methods. However, when loaded and executed, the proxy program will ~ accomplish the monitored data transfers as described for the client computers of the other preferred embodiments herein. In a preferred embodiment, the proxy may share common main memory with the actual client computer, wherein interrupts o r flags may be used for communication between the proxy and the actual client. fn other well known implementations where the proxy is a smart peripheral, or a smart modem peripheral to the actual c I i a n t computer, well known techniques of handshaking, flags, and interrupts may be used. Such systems may be designed with flexibility as known in the art. For example, a s m a rt peripheral may be arranged to accomplish some transfers under a priority basis while other transfers may be accomplished during low activity periods. Such control o f the timing of transfers by proxy are well known.
In one embodiment of the present invention, the c I i a n t program may. be implemented as a computer program, f o r example in the "C++" programming language and compiled for execution on the desired platform, such as a machine with a Windows95 operating system. The program also may be implemented, for example, in the Java programming language, where a browser would execute the Java program to download the requested file. I n general, this program, when executed, has the capability of transferring files from a server computer over a network using an application protocol to communicate with the file transfer server. This client program may be implemented by using at least the read commands available in FTP. The client program has, in addition, the capability to monitor a download operation while i t occurs and to automatically restart or continue the download from the point where an interrupt occurs. i n one embodiment, a user may specify a time at which the program will be executed to initiate the download. A
user may also specify alternative parameters for a download, such as a connection location or another copy of the file to be downloaded.
On the server computer, the file transfer server also may be implemented as a computer program, for example, in the "C" programming language, and compiled f o r execution on the desired platform, such a machine with a UNIX or WindowsNT operating system. In general, this program, when executed, has the capability o f handling client requests to transfer files over a network.
Using the same application protocol defined with the client program. For example, the file transfer server may be implemented as an FTP server. In addition, the file transfer server has the capability of opening, reading and transmitting data starting from a specified offset i n a data file, where the offset is parameter received fro m a client, typically as a part of a request from t h a c I i a n t to read a particular data file.
One embodiment of the invention will now be described in connection with Fig. 4. in this embodiment, the f i I a transfer server is referred to as a download server 122 which is separate from a standard FTP server 120 operating on the same machine. Because the download server would not be assigned a well-known port according to Internet standards, a client program would need to locate the download server.
The server computer includes the FTP server 120 that communicates using ports 126, which are port numbers 20 and 21 according to convention for the Internet. The download server 122 also is provided on a port 124 which could be any of a number of ports available on the server computer. It is possible that this port could vary fro m one server computer to another server computer.
Accordingly, the indication of the port number "x" i s stored in a file at the time the download server i s instantiated or executed on the machine, after it has been assigned a port number. This file is preferably stored i n the same location with respect to an FTP server on the same machine, and thus will have a predetermined name and path, e.g., "download/port_file." The absence o f this file should indicate that the download server i s unavailable.
When the client computer executes the client program, the executed client program 18 communicates with the FTP server 120 to retrieve the port file as indicated a t 128. This port file is returned in step 142 to the client as indicated in 130. The client reads the port file t o obtain the port number for the download server 122. The client can then communicate with the download server via messages sent to port "x."
One embodiment of the process performed by the execute client program 18, and particularly module 22, for initiating and monitoring a download will now be described in more detail connection with Figs. 5 and 6.
This process may begin when the client program is executed or at a specified time. For example, if the client program is downloaded with Internet Explorer browser, this browser requests input from the user t o indicate whether the file should be opened (executed) o r saved. If the file is saved, it can be executed at a later time.
When executed, the client program may request a user to specify a time for the download to occur, using any appropriate user interface, or a time may be automatically specified. When the download begins, a variable value, indicative of the total bytes received, i s initialized to zero in step 50. This number will be used to determine how much of a data file has been received, in case a failure occurs during the download process.
Next, if necessary, the client connects to the Internet i n step 52. The connection may be initiated by an automatic dial-up connection to an Internet service provider and/or by assignment of an IP address to the client, if necessary, or by any other means. A test for an existing connection also can be made. If a failure occurs, as tested for i n step 54, a connection attempt in step 52 may be performed again. An alternate connection also may be attempted. Otherwise, the client initiates an FTP
transfer to retrieve the file indicating the port number of the download server by sending a message to the FTP
server including a user name and password, if necessary, in step 56. This message establishes a connection between the FTP server and the executed client program.
User names and passwords commonly are used when the FTP protocol is used to download files. If a fai I a re occurs, as determined in step 58, the process may be restarted, for example by returning to step 56 or step 52, depending on the type of error. It is possible t o implement the system so that it waits, in step 60, i n order to allow time before resending a message, f o r example to allow time for a system failure to be remedied.
If the user name and password are successfully sent i n step 56, the type of transfer to be performed is then sent to the FTP server in step 62. This is another form of FTP
message. If this step is successfully completed, the client's port is then sent to the server in step 66, t o inform the FTP server which port on the client machine will receive the data. If this command i s completed successfully, a command to retrieve the f i I a containing the port number of the download server is sent to the FTP server in step 68. The client program may specify the file, for example, by using a uniform resource locator (URL). A URL is defined by an Internet Request For Comments (RFC) document. It includes an indicator of a protocol (e.g., ftp or http or other protocol), a site (e.g., ethos.com), and a path (e.g., "a/b/c/filename.txt") for a specific file. It also may include a delimiter, e.g., "?," after which parameters may be added. A URL thus may look like the following:
ftp://ethos.com/a/b/c/filename.txt?parameter.
If either step 62 or 66 fails, as determined in step 64 and 67, respectively, the process can be restarted, possibly including the wait step 60, and returning t o either step 52 or 56 depending on the type of error.
After the client sends the retrieve file command, the FTP
server transmits the port file to the specified port at the client. The client then reads and stores the data. I f this read is not successful, retries are performed. I t should also be indicated that, as illustrated at 72, that the number of retries may be limited by number or by time. If the read operations are reliably completed, the client then in step 74 proceeds to transfer the desired file from the download server by sending read requests to the port designated in the port file, as described in more detail below in connection with Fig. 6.
Referring now to Fig. 6, one embodiment of the process of transferring data to the client from the download server will now be described. First, the client establishes in step 76 a connection with the download server in a manner similar to how a connection i s established with the FTP server. If an error occurs, the error can be reported to the user or an alternate connection may be tried. A filename for a data file f o r receiving the downloaded file is specified in step 77.
This may be done through any appropriate user interface.
If the file does not exist, as determined in step 78, it i s created an opened in write mode in step 79, otherwise i t is opened in append mode in step 80. The client then sends a read request to the download server, and a specified offset, in step 81. Processing by the download server to send the data is described in more detail below in connection with Fig. 7.
Data received at the client is read from a socket (a construct in the TCP/IP protocol) at the indicated port i n step 82, for example, using the "recv()" command. If the data read from the socket indicates that valid data is not available, as determined in step 84, e.g., by returning " -1," the socket is continually read by returning to step 82, subject to a time out operation as determined in step 92.
If a time out occurs, the file on the client is closed, and the process of downloading automatically restarts w i t h step 76, of reestablishing the connection w i t h the download server. The automatic restarts from step 76 also may be limited, in number or in time, allowing automatic restart, for example, from step 52 or 56 of Fig.
5. If valid data is read in step 84, then an end of f i I a condition is checked in step 88. For example, the "recv()"
command may return "0." if an end of file is reached, the read operation is complete and the client's data f i I a m ay be closed. Otherwise, the data read from the socket i s written to the data file at the client in step 86. The current total number of bytes reliably received is updated in step 90 and more data is read from the socket in step 82.
Having now described an embodiment of the c I i a n t program, an embodiment of the download server program in accordance with the invention will now be described with reference to Fig. 7. Fig. 7 describes, in particular, how the download server processes a request f o r a portion of a file. The download server receives a command in step 99 from the client requesting a data file. It obtains the parameters of this command in step 100. The parameters in this instance include a file name and offset. The file is then opened to receive a f i I a pointer in step 102. This operation can be performed, f o r example, using the "fopen" command in the "C" computer programming language.
If the offset is equal to zero, determined in step 104, then data is read starting from the indicated file pointer in step 106 and transmitted to the client using the TCP/IP protocol over the network. If the offset is not equal to zero, the file pointer is updated to the specified offset. Then the data is read from the data file in step 10fi starting from the updated pointer location.
The pointer location may be updated, for example by using the "fseek" command in the "C" programming language. The data read is then sent to the client in step 107.
Using a client and server as described above, several benefits are provided. For example, a user may download information at a site at a specified time, typically when the network has less traffic, which should increase the speed of transfer and reduce the likelihood of errors.
By automatically initiating the connection and download at a specified time, a user also does not need to be present at the computer to start the download. By using a client that monitors a download and automatically restarting the download from the offset at which a failure occurs, the user does not need to be present t o make sure a download is successful. By using a server which starts reading and sending data from a data f i I a from a specified offset within the data f i I a , an interrupted download may be restarted where it I a f t off. The combination of this client and server system increase the likelihood of success of the download, eliminate unnecessary data transfer, while eliminating the need for interaction with an individual.
Having now described a few embodiments of the invention, it should be apparent to those skilled in the art that the foregoing is merely illustrative and not limiting, having been presented by way of example only.
Numerous modifications and other embodiments are within the scope of one of ordinary skill in the art. For example, other network protocols and other f i I a transfer protocols operating over such networks may be used. The system also may allow retries using various alternatives to download the data. These and other modifications are contemplated as falling within the scope of the invention as defined by the appended claims and equivalent thereto.
command may return "0." if an end of file is reached, the read operation is complete and the client's data f i I a m ay be closed. Otherwise, the data read from the socket i s written to the data file at the client in step 86. The current total number of bytes reliably received is updated in step 90 and more data is read from the socket in step 82.
Having now described an embodiment of the c I i a n t program, an embodiment of the download server program in accordance with the invention will now be described with reference to Fig. 7. Fig. 7 describes, in particular, how the download server processes a request f o r a portion of a file. The download server receives a command in step 99 from the client requesting a data file. It obtains the parameters of this command in step 100. The parameters in this instance include a file name and offset. The file is then opened to receive a f i I a pointer in step 102. This operation can be performed, f o r example, using the "fopen" command in the "C" computer programming language.
If the offset is equal to zero, determined in step 104, then data is read starting from the indicated file pointer in step 106 and transmitted to the client using the TCP/IP protocol over the network. If the offset is not equal to zero, the file pointer is updated to the specified offset. Then the data is read from the data file in step 10fi starting from the updated pointer location.
The pointer location may be updated, for example by using the "fseek" command in the "C" programming language. The data read is then sent to the client in step 107.
Using a client and server as described above, several benefits are provided. For example, a user may download information at a site at a specified time, typically when the network has less traffic, which should increase the speed of transfer and reduce the likelihood of errors.
By automatically initiating the connection and download at a specified time, a user also does not need to be present at the computer to start the download. By using a client that monitors a download and automatically restarting the download from the offset at which a failure occurs, the user does not need to be present t o make sure a download is successful. By using a server which starts reading and sending data from a data f i I a from a specified offset within the data f i I a , an interrupted download may be restarted where it I a f t off. The combination of this client and server system increase the likelihood of success of the download, eliminate unnecessary data transfer, while eliminating the need for interaction with an individual.
Having now described a few embodiments of the invention, it should be apparent to those skilled in the art that the foregoing is merely illustrative and not limiting, having been presented by way of example only.
Numerous modifications and other embodiments are within the scope of one of ordinary skill in the art. For example, other network protocols and other f i I a transfer protocols operating over such networks may be used. The system also may allow retries using various alternatives to download the data. These and other modifications are contemplated as falling within the scope of the invention as defined by the appended claims and equivalent thereto.
Claims (23)
1. A process for downloading a data file from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer, wherein the process has an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer, comprising the steps, performed by the client computer, of:
initiating a download of the data file by sending, using the application protocol, a request for the data file to the server computer over the computer network;
monitoring data received from the server computer as a stream of data in response to the request for the data file to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client;
storing the amount of data successfully received by the client when an error is detected that terminates the download; and in response to a detected error that terminates the download of the data file, automatically restarting the download of the data file by initiating a second download of the data file by sending, using the application protocol, a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
initiating a download of the data file by sending, using the application protocol, a request for the data file to the server computer over the computer network;
monitoring data received from the server computer as a stream of data in response to the request for the data file to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client;
storing the amount of data successfully received by the client when an error is detected that terminates the download; and in response to a detected error that terminates the download of the data file, automatically restarting the download of the data file by initiating a second download of the data file by sending, using the application protocol, a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
2. The process of claim 1, wherein the step of initiating the download comprises the steps, performed by the client, of:
sending a message to the server computer using a second application protocol requesting an indication of a port for a server process for performing the download;
receiving the indicator of the port; and sending a message to the server process using the application protocol at the indicated port requesting the data file.
sending a message to the server computer using a second application protocol requesting an indication of a port for a server process for performing the download;
receiving the indicator of the port; and sending a message to the server process using the application protocol at the indicated port requesting the data file.
3. The process of claim 1, wherein the step of initiating the download comprises the steps, performed by the client computer, of:
receiving from a user a specified time for performing the download of the data file; and sending the request for the data file to the server computer at the specified time.
receiving from a user a specified time for performing the download of the data file; and sending the request for the data file to the server computer at the specified time.
4. A process for downloading a data file from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer, wherein the process sends data over a computer network connecting the client computer to the server computer, comprising the steps, performed by the client computer, of:
sending a request for a client program to the server computer over the computer network;
receiving from the server computer, in response the request for the client program, a client program which when executed performs the steps of:
initiating a download of the data file by sending a request for the data file to the server computer over the computer network;
monitoring data received from the server computer in response to the request for the data file to detect termination of the download o f the data file;
in response to a detected error that terminates the download of the data file, automatically restarting the download of the data file by sending a request for the data file to the server computer.
sending a request for a client program to the server computer over the computer network;
receiving from the server computer, in response the request for the client program, a client program which when executed performs the steps of:
initiating a download of the data file by sending a request for the data file to the server computer over the computer network;
monitoring data received from the server computer in response to the request for the data file to detect termination of the download o f the data file;
in response to a detected error that terminates the download of the data file, automatically restarting the download of the data file by sending a request for the data file to the server computer.
5. The process of claim 4, wherein the step of monitoring comprises the steps of:
tracking an amount of data from the data file successfully received by the client; and storing the amount of data successfully received when an error is detected that terminates the download.
tracking an amount of data from the data file successfully received by the client; and storing the amount of data successfully received when an error is detected that terminates the download.
6. The process of claim 5, wherein the step of automatically restarting the download of the data file comprises the step of:
initiating a second download of the data file by sending a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
initiating a second download of the data file by sending a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
7. The process of claim 6, wherein the application protocol sends data as a stream of data.
8. The process of claim 4, wherein the step of initiating the download comprises the steps, performed by the client, of:
sending a message to the server computer requesting an indication of a port for a server process for performing the download;
receiving the indicator of the port; and sending a message to the server process at the indicated port requesting the data file.
sending a message to the server computer requesting an indication of a port for a server process for performing the download;
receiving the indicator of the port; and sending a message to the server process at the indicated port requesting the data file.
9. The process of claim 4, wherein the client program, when executed, further performs the step of:
receiving from a user a specified time for performing the download of the data file; and sending the request for the data file to the server computer at the specified time.
receiving from a user a specified time for performing the download of the data file; and sending the request for the data file to the server computer at the specified time.
10. A client system for downloading a data file from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer, wherein the client system uses an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer, comprising:
means for initiating a download of the data file by sending, using the application protocol, a request for the data file to the server computer over the computer network;
means for monitoring data received from the server computer as a stream of data in response to the request for the data file to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client;
means for storing the amount of data successfully received by the client when an error is detected that terminates the download; and means, operative in response to a detected error that terminates the download of the data file, for automatically restarting the download of the data file by initiating a second download of the data file by sending, using the application protocol, a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
means for initiating a download of the data file by sending, using the application protocol, a request for the data file to the server computer over the computer network;
means for monitoring data received from the server computer as a stream of data in response to the request for the data file to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client;
means for storing the amount of data successfully received by the client when an error is detected that terminates the download; and means, operative in response to a detected error that terminates the download of the data file, for automatically restarting the download of the data file by initiating a second download of the data file by sending, using the application protocol, a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
11. The client system of claim 10, wherein the means for initiating the download comprises:
means for sending a message to the server computer using a second application protocol requesting an indication of a port for a server process for performing the download;
means for receiving the indicator of the port; and means for sending a message to the server process using the application protocol at the indicated port requesting the data file.
means for sending a message to the server computer using a second application protocol requesting an indication of a port for a server process for performing the download;
means for receiving the indicator of the port; and means for sending a message to the server process using the application protocol at the indicated port requesting the data file.
12. The client system of claim 10, wherein the means for initiating the download comprises:
means for receiving from a user a specified time for performing the download of the data file; and means for sending the request for the data file to the server computer at the specified time.
means for receiving from a user a specified time for performing the download of the data file; and means for sending the request for the data file to the server computer at the specified time.
13. A client system for downloading a data file from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer, wherein the client system sends data over a computer network connecting the client computer to the server computer, comprising:
means for sending a request for a client program to the server computer over the computer network;
means for receiving from the server computer, in response the request for the client program, such that the client system, when the client program is executed, comprises:
means for initiating a download of the data file by sending a request for the data file to the server computer over the computer network;
means for monitoring data received from the server computer in response to the request for the data file to detect termination of the download of the data file;
means, operative in response to a detected error that terminates the download of the data file, for automatically restarting the download of the data file by sending a request for the data file to the server computer.
means for sending a request for a client program to the server computer over the computer network;
means for receiving from the server computer, in response the request for the client program, such that the client system, when the client program is executed, comprises:
means for initiating a download of the data file by sending a request for the data file to the server computer over the computer network;
means for monitoring data received from the server computer in response to the request for the data file to detect termination of the download of the data file;
means, operative in response to a detected error that terminates the download of the data file, for automatically restarting the download of the data file by sending a request for the data file to the server computer.
14. The client system of claim 13, wherein the means for monitoring comprises:
means for tracking an amount of data from the data file successfully received by the client; and means for storing the amount of data successfully received when an error is detected that terminates the download.
means for tracking an amount of data from the data file successfully received by the client; and means for storing the amount of data successfully received when an error is detected that terminates the download.
15. The client system of claim 14, wherein the means for automatically restarting the download of the data file comprises:
means for initiating a second download of the data file by sending a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
means for initiating a second download of the data file by sending a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
16. The client system of claim 15, wherein the application protocol sends data as a stream of data.
17. The client system of claim 13, wherein the means for initiating the download comprises: means for sending a message to the server computer requesting an indication of a port for a server process for performing the download;
means for receiving the indicator of the port; and means for sending a message to the server process at the indicated port requesting the data file.
means for receiving the indicator of the port; and means for sending a message to the server process at the indicated port requesting the data file.
18. The client system of claim 13, wherein the client system, when the client program is executed, further comprises:
means for receiving from a user a specified time for performing the download of the data file; and means for sending the request for the data file to the server computer at the specified time.
means for receiving from a user a specified time for performing the download of the data file; and means for sending the request for the data file to the server computer at the specified time.
19. A process for downloading a data file from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer, wherein the process uses an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer, comprising the steps, performed by the server computer, of:
receiving a request, using the application protocol, for the data file from the client computer over the computer network;
reading data from the data file and sending the data as a stream of data to the client computer using the application protocol;
after termination of the sending of the data by the application protocol, receiving a request for the data file from the client computer, wherein the request specifies the amount of data successfully received; and reading data from the data file starting from an offset determined according to the specified amount of data and sending the data as a stream of data to the client computer using the application protocol.
receiving a request, using the application protocol, for the data file from the client computer over the computer network;
reading data from the data file and sending the data as a stream of data to the client computer using the application protocol;
after termination of the sending of the data by the application protocol, receiving a request for the data file from the client computer, wherein the request specifies the amount of data successfully received; and reading data from the data file starting from an offset determined according to the specified amount of data and sending the data as a stream of data to the client computer using the application protocol.
20. A server system for downloading a data file from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer, wherein the server system uses an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client computer to the server computer, the server system comprising:
means for receiving a request, using the transfer protocol, for the data file from the client computer over the computer network;
means, operative in response to the request, for reading data from the data file and for sending the data as a stream of data to the client computer using the application protocol;
means, operative after termination of the sending of the data by the application protocol, receiving a request for the data file from the client computer, wherein the request specifies the amount of data successfully received; and means for reading data from the data file starting from an offset determined according to the specified amount of data and for sending the data as a stream of data to the client computer using the application protocol.
means for receiving a request, using the transfer protocol, for the data file from the client computer over the computer network;
means, operative in response to the request, for reading data from the data file and for sending the data as a stream of data to the client computer using the application protocol;
means, operative after termination of the sending of the data by the application protocol, receiving a request for the data file from the client computer, wherein the request specifies the amount of data successfully received; and means for reading data from the data file starting from an offset determined according to the specified amount of data and for sending the data as a stream of data to the client computer using the application protocol.
21. Computer-readable medium having stored thereon sequences of instructions which, when executed by a computer processing system having a server computer connected via a communications network to a client computer, cause the computer processing system to perform the steps of:
initiating a download of the data file by sending, using an application protocol, a request for a data file to the server computer over the communications network;
monitoring data received from the server computer as a stream of data in response to the request for the data file to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client computer;
storing the amount of data successfully received by the client when an error is detected that terminates the download; and in response to a detected error that terminates the download of the data file, automatically restarting the download of the data file by initiating a second download of the data file by sending, using the application protocol, a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
initiating a download of the data file by sending, using an application protocol, a request for a data file to the server computer over the communications network;
monitoring data received from the server computer as a stream of data in response to the request for the data file to detect termination of the download of the data file and to track an amount of data from the data file successfully received by the client computer;
storing the amount of data successfully received by the client when an error is detected that terminates the download; and in response to a detected error that terminates the download of the data file, automatically restarting the download of the data file by initiating a second download of the data file by sending, using the application protocol, a request for the data file to the server computer, wherein the request specifies the amount of data successfully received.
22. A client system for downloading a data file from a server computer to a client computer, wherein the data file is stored on a computer readable medium connected to the server computer, wherein the client system uses an application protocol for sending data as a stream of data using a transport protocol over a computer network connecting the client system to the server computer, comprising:
a proxy computing system, a client computing system in communication with said proxy computing system, means for initiating a download of the data file by sending, using the application protocol, a request from said proxy computing system for the data file to the server computer over the computer network;
means for detecting an error in the downloading of the data file, means for tracking the amount of data successfully downloaded to the proxy computing system;
means for storing the data, within said proxy computing system, downloaded before said error detected , and means, responsive to said detected error and said amount of data successfully downloaded, for automatically initiating a second download of the data file that was unsuccessfully downloaded.
a proxy computing system, a client computing system in communication with said proxy computing system, means for initiating a download of the data file by sending, using the application protocol, a request from said proxy computing system for the data file to the server computer over the computer network;
means for detecting an error in the downloading of the data file, means for tracking the amount of data successfully downloaded to the proxy computing system;
means for storing the data, within said proxy computing system, downloaded before said error detected , and means, responsive to said detected error and said amount of data successfully downloaded, for automatically initiating a second download of the data file that was unsuccessfully downloaded.
23. The system as defined in claim 22 wherein said proxy computing system comprises:
an intelligent computer peripheral of said client computer dedicated to performing said downloading, and means for transferring said data file from said proxy computing system to the client computer.
an intelligent computer peripheral of said client computer dedicated to performing said downloading, and means for transferring said data file from said proxy computing system to the client computer.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/804,902 | 1997-02-24 | ||
US08804902 US6049892C1 (en) | 1997-02-24 | 1997-02-24 | Process and apparatus for downloading data from a server computer to a client computer |
PCT/US1998/003534 WO1998039707A1 (en) | 1997-02-24 | 1998-02-24 | Process and apparatus for downloading data from a server computer to a client computer |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2281672A1 true CA2281672A1 (en) | 1998-09-11 |
Family
ID=25190164
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002281672A Abandoned CA2281672A1 (en) | 1997-02-24 | 1998-02-24 | Process and apparatus for downloading data from a server computer to a client computer |
Country Status (6)
Country | Link |
---|---|
US (2) | US6049892C1 (en) |
EP (1) | EP1019816A4 (en) |
JP (1) | JP2002510412A (en) |
AU (1) | AU742817B2 (en) |
CA (1) | CA2281672A1 (en) |
WO (1) | WO1998039707A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11169899B2 (en) * | 2019-04-15 | 2021-11-09 | Toyota Motor Engineering & Manufacturing North America, Inc. | Mitigating data offsets for machine learning |
Families Citing this family (172)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6471866B1 (en) * | 1996-11-13 | 2002-10-29 | Transgenomic, Inc. | Process for performing polynucleotide separations |
US6049892C1 (en) * | 1997-02-24 | 2002-06-04 | Ethos Software Corp | Process and apparatus for downloading data from a server computer to a client computer |
US6216163B1 (en) * | 1997-04-14 | 2001-04-10 | Lucent Technologies Inc. | Method and apparatus providing for automatically restarting a client-server connection in a distributed network |
JPH11143760A (en) * | 1997-10-23 | 1999-05-28 | Internatl Business Mach Corp <Ibm> | File transferring device and method therefor |
US6418478B1 (en) | 1997-10-30 | 2002-07-09 | Commvault Systems, Inc. | Pipelined high speed data transfer mechanism |
US7209972B1 (en) * | 1997-10-30 | 2007-04-24 | Commvault Systems, Inc. | High speed data transfer mechanism |
JP3906535B2 (en) * | 1997-11-07 | 2007-04-18 | ソニー株式会社 | Download system and recording medium |
US6615383B1 (en) * | 1998-05-29 | 2003-09-02 | Sun Microsystems, Inc. | System and method for message transmission between network nodes connected by parallel links |
SE513353C2 (en) * | 1998-10-21 | 2000-08-28 | Ericsson Telefon Ab L M | Partial image retrieval in the compressed domain |
US20030195974A1 (en) * | 1998-12-04 | 2003-10-16 | Ronning Joel A. | Apparatus and method for scheduling of search for updates or downloads of a file |
US7617124B1 (en) | 1998-12-04 | 2009-11-10 | Digital River, Inc. | Apparatus and method for secure downloading of files |
US7058597B1 (en) | 1998-12-04 | 2006-06-06 | Digital River, Inc. | Apparatus and method for adaptive fraud screening for electronic commerce transactions |
JP4738556B2 (en) * | 1998-12-28 | 2011-08-03 | 富士通株式会社 | Distributed operation system and recording medium |
JP2000207219A (en) * | 1999-01-18 | 2000-07-28 | Fujitsu Ten Ltd | Communication system for between on-vehicle terminal and center, and the on-vehicle terminal used for communication system |
KR100684986B1 (en) | 1999-12-31 | 2007-02-22 | 주식회사 잉카인터넷 | Online dangerous information screening system and method |
SE521109C2 (en) * | 1999-04-23 | 2003-09-30 | Corus Technologies Ab | Method and apparatus for integrating a number of computerized client systems |
US7197144B1 (en) | 1999-06-08 | 2007-03-27 | Ethos Technologies, Inc. | Method and apparatus to authenticate a user's system to prevent unauthorized use of software products distributed to users |
US6490616B1 (en) * | 1999-06-14 | 2002-12-03 | Wind River International, Ltd. | Method and apparatus for incremental download from server to client |
US7035880B1 (en) | 1999-07-14 | 2006-04-25 | Commvault Systems, Inc. | Modular backup and retrieval system used in conjunction with a storage area network |
JP3916806B2 (en) * | 1999-07-26 | 2007-05-23 | 富士通株式会社 | Remote loading execution method, remote loading execution system, information processing apparatus, management apparatus, and computer-readable recording medium |
JP2001051923A (en) * | 1999-08-11 | 2001-02-23 | Ntt Comware Corp | System supervising device, distribution result managing device, distribution result display terminal device, distribution information management system, and their control method and recording medium |
US6427149B1 (en) * | 1999-09-09 | 2002-07-30 | Herman Rodriguez | Remote access of archived compressed data files |
US6907463B1 (en) * | 1999-10-19 | 2005-06-14 | Audiogalaxy, Inc. | System and method for enabling file transfers executed in a network environment by a software program |
US6748450B1 (en) * | 1999-10-28 | 2004-06-08 | International Business Machines Corporation | Delayed delivery of web pages via e-mail or push techniques from an overloaded or partially functional web server |
US6928468B2 (en) * | 1999-10-29 | 2005-08-09 | Koninklijke Philips Electronics N.V. | System for broadcasting software applications and portable data communications device for use in such a system |
US6339785B1 (en) * | 1999-11-24 | 2002-01-15 | Idan Feigenbaum | Multi-server file download |
US20030050832A1 (en) * | 1999-12-08 | 2003-03-13 | Jacobs Paul E. | E-mail software and method and system for distributing advertisements to client devices that have such E-mail software installed thereon |
US20010044741A1 (en) * | 1999-12-08 | 2001-11-22 | Jacobs Paul E. | E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon |
US7103643B1 (en) * | 1999-12-08 | 2006-09-05 | Qualcomm Inc | E-mail software and method and system for distributing advertisements to client devices that have such E-mail software installed thereon |
AU1954401A (en) * | 1999-12-08 | 2001-06-18 | Qualcomm Incorporated | System for distributing advertisements to client devices |
JP2004500637A (en) * | 1999-12-08 | 2004-01-08 | クゥアルコム・インコーポレイテッド | E-mail software and method and system for distributing advertisements to client devices |
US20010044736A1 (en) * | 1999-12-08 | 2001-11-22 | Jacobs Paul E. | E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon |
US20010047408A1 (en) * | 1999-12-08 | 2001-11-29 | Jacobs Paul E. | E-mail software and method and system for distributing advertisements to client devices that have such E-mail software installed thereon |
US20020029166A1 (en) * | 1999-12-08 | 2002-03-07 | Qualcomm Incorporated | E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon |
AU8030500A (en) * | 1999-12-08 | 2001-06-18 | Qualcomm Incorporated | Monitoring user interaction with web advertisements |
US20070005428A1 (en) * | 1999-12-08 | 2007-01-04 | Jacobs Paul E | Method for distributing advertisements to client devices having e-mail software installed including multiple advertisement operational modes |
US20020072967A1 (en) * | 1999-12-08 | 2002-06-13 | Jacobs Paul E. | System for controlling the distribution of advertisements to informational client devices |
US20030149738A1 (en) * | 1999-12-08 | 2003-08-07 | Jacobs Paul E. | E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon |
US8712848B2 (en) * | 1999-12-08 | 2014-04-29 | Qualcomm Incorporated | Method for distributing advertisements to client devices using an obscured ad monitoring function |
US20070038728A1 (en) * | 1999-12-08 | 2007-02-15 | Jacobs Paul E | A system for controlling the distribution of advertisements to informational client devices using a playlist |
US6522268B2 (en) | 2000-01-05 | 2003-02-18 | Realnetworks, Inc. | Systems and methods for multiple-file data compression |
US6377974B1 (en) * | 2000-01-19 | 2002-04-23 | Speedbit Ltd. | Methods and apparatus for downloading a file from a server |
US7003641B2 (en) | 2000-01-31 | 2006-02-21 | Commvault Systems, Inc. | Logical view with granular access to exchange data managed by a modular data and storage management system |
US6658436B2 (en) | 2000-01-31 | 2003-12-02 | Commvault Systems, Inc. | Logical view and access to data managed by a modular data and storage management system |
ES2374388T3 (en) | 2000-02-01 | 2012-02-16 | Commvault Systems, Inc. | HIGH-SPEED DATA TRANSFER MECHANISM. |
US6853985B1 (en) * | 2000-02-16 | 2005-02-08 | Ricoh Microelectronics, Company, Ltd. | Media information distribution and recording system, and apparatus and program-recorded medium for the system |
US8055776B1 (en) | 2000-04-05 | 2011-11-08 | International Business Machines Corporation | Sending full-content data to a second data processing system while viewing reduced-content data on a first data processing system |
US6460163B1 (en) * | 2000-04-05 | 2002-10-01 | International Business Machines Corporation | Software and method for digital content vending and transport |
US6937814B1 (en) * | 2000-04-14 | 2005-08-30 | Realnetworks, Inc. | System and method for play while recording processing |
IL142802A (en) * | 2000-04-27 | 2015-01-29 | Enzo Therapeutics Inc | Use of one or more hbv antigens for the preparation of oral pharmaceutical compositions for treating a subject having an active hbv infection or hepatocellular carcinoma |
US6724720B1 (en) | 2000-05-01 | 2004-04-20 | Palmone, Inc. | Swapping a nonoperational networked electronic system for an operational networked electronic system |
US7391718B2 (en) * | 2004-03-09 | 2008-06-24 | Palm, Inc. | Swapping a nonoperational networked electronic system for an operational networked electronic system |
US6928481B1 (en) * | 2000-05-05 | 2005-08-09 | International Business Machines Corporation | Method, apparatus and program to optimize the network distribution of digital information based on hierarchical grouping of server topology and code distribution |
WO2002011350A1 (en) * | 2000-07-31 | 2002-02-07 | Siemens Aktiengesellschaft | Method for correcting errors in a packet-oriented data transmission |
JP2002123449A (en) * | 2000-08-02 | 2002-04-26 | Sanyo Electric Co Ltd | Information distributing device |
JP4490566B2 (en) * | 2000-09-13 | 2010-06-30 | 株式会社日立製作所 | Terminal device and navigation server |
JP2002191039A (en) * | 2000-10-11 | 2002-07-05 | Matsushita Electric Ind Co Ltd | State management method for terminal and its system |
US6725290B1 (en) * | 2000-11-08 | 2004-04-20 | Enfora, Inc. | Persistent modem connection |
US6826581B2 (en) * | 2000-12-06 | 2004-11-30 | Intel Corporation | Upgrading a device over a network by downloading results of command execution from script file |
US7085744B2 (en) * | 2000-12-08 | 2006-08-01 | International Business Machines Corporation | Method and system for conducting a transaction over a network |
CA2430099A1 (en) * | 2000-12-20 | 2002-06-27 | International Business Machines Corporation | Method and system for remote software distribution and installation |
US6993508B1 (en) | 2000-12-29 | 2006-01-31 | Novell, Inc. | Method and mechanism for vending digital content |
EP1239644A1 (en) * | 2001-03-08 | 2002-09-11 | THOMSON multimedia | Method for managing isochronous file transfers in a HAVI environment |
WO2002075571A1 (en) * | 2001-03-16 | 2002-09-26 | Otg Software, Inc. | Network file sharing method and system |
US8402005B2 (en) * | 2001-03-27 | 2013-03-19 | Intel Corporation | Systems and methods for creating self-extracting files |
JP2002312227A (en) * | 2001-04-18 | 2002-10-25 | Toshiba Corp | Portable equipment |
US7272645B2 (en) | 2001-05-25 | 2007-09-18 | Sbc Technology Resources, Inc. | Method of improving the reliability of peer-to-peer network downloads |
US6757735B2 (en) * | 2001-07-03 | 2004-06-29 | Hewlett-Packard Development Company, L.P. | Method for distributing multiple description streams on servers in fixed and mobile streaming media systems |
JP4860070B2 (en) * | 2001-08-30 | 2012-01-25 | 株式会社日立製作所 | File transmission method and file transmission system |
US20030084165A1 (en) * | 2001-10-12 | 2003-05-01 | Openwave Systems Inc. | User-centric session management for client-server interaction using multiple applications and devices |
CN1161924C (en) * | 2002-04-02 | 2004-08-11 | 华为技术有限公司 | Data upgrading method of two-layer exchange equipment |
US7233790B2 (en) * | 2002-06-28 | 2007-06-19 | Openwave Systems, Inc. | Device capability based discovery, packaging and provisioning of content for wireless mobile devices |
US7299033B2 (en) | 2002-06-28 | 2007-11-20 | Openwave Systems Inc. | Domain-based management of distribution of digital content from multiple suppliers to multiple wireless services subscribers |
US7302479B2 (en) * | 2002-07-23 | 2007-11-27 | International Business Machines Corporation | Dynamic client/server session recovery in a heterogenous computer network |
GB2409553B (en) | 2002-09-16 | 2007-04-04 | Commvault Systems Inc | System and method for optimizing storage operations |
KR20040032205A (en) * | 2002-10-01 | 2004-04-17 | 삼성전자주식회사 | Apparatus and method for providing help function |
US6760794B2 (en) | 2002-11-22 | 2004-07-06 | Honda Giken Kogyo Kabushiki Kaisha | Method for decreasing downtime in vehicle identification number stamping operations |
JP2004227080A (en) * | 2003-01-20 | 2004-08-12 | Nec Corp | Information processing system, mobile terminal, and information processing server |
US7925771B1 (en) | 2003-03-03 | 2011-04-12 | Realnetworks, Inc. | System and method for uninterrupted streaming |
US8117327B2 (en) * | 2003-05-08 | 2012-02-14 | Jda Software Group, Inc. | Data integration system with programmatic source and target interfaces |
US8108534B2 (en) * | 2003-05-08 | 2012-01-31 | Jda Software Group, Inc. | Data integration system with programmatic source and target interfaces |
US8117326B2 (en) * | 2003-05-08 | 2012-02-14 | Jda Software Group, Inc. | Data integration system with programmatic source and target interfaces |
US7454569B2 (en) | 2003-06-25 | 2008-11-18 | Commvault Systems, Inc. | Hierarchical system and method for performing storage operations in a computer network |
CN1315053C (en) * | 2003-09-15 | 2007-05-09 | 联想(北京)有限公司 | Refresh method of network computer BIOS |
US9100814B2 (en) * | 2003-09-17 | 2015-08-04 | Unwired Plant, Llc | Federated download of digital content to wireless devices |
CA2539254A1 (en) * | 2003-09-18 | 2005-04-14 | Field2Base, Inc. | Job site communications systems, methods, and computer program products |
US7529782B2 (en) | 2003-11-13 | 2009-05-05 | Commvault Systems, Inc. | System and method for performing a snapshot and for restoring data |
US7613748B2 (en) | 2003-11-13 | 2009-11-03 | Commvault Systems, Inc. | Stored data reverification management system and method |
WO2005050381A2 (en) | 2003-11-13 | 2005-06-02 | Commvault Systems, Inc. | Systems and methods for performing storage operations using network attached storage |
JP4536383B2 (en) * | 2004-01-16 | 2010-09-01 | 株式会社エヌ・ティ・ティ・ドコモ | Data receiving apparatus and data receiving method |
US7596285B2 (en) * | 2004-02-26 | 2009-09-29 | International Business Machines Corporation | Providing a portion of an electronic mail message at a reduced resolution |
US7512658B2 (en) * | 2004-02-26 | 2009-03-31 | International Business Machines Corporation | Providing a portion of an electronic mail message based upon a transfer rate, a message size, and a file format |
US20050193069A1 (en) * | 2004-02-26 | 2005-09-01 | International Business Machines Corporation | Providing a portion of an electronic mail message based upon a transfer rate and a message size |
US20050193145A1 (en) * | 2004-02-26 | 2005-09-01 | International Business Machines Corporation | Providing a portion of an electronic mail message based upon digital rights |
KR100557192B1 (en) * | 2004-04-06 | 2006-03-03 | 삼성전자주식회사 | Method for sending data in case of irregularity completion in data synchronization between server and client and system therefor |
CN1681033A (en) * | 2004-04-06 | 2005-10-12 | 皇家飞利浦电子股份有限公司 | Fault correcting mechanism for CD player |
US20060047855A1 (en) | 2004-05-13 | 2006-03-02 | Microsoft Corporation | Efficient chunking algorithm |
US7631098B2 (en) * | 2004-06-08 | 2009-12-08 | International Business Machines Corporation | Method, system and program product for optimized concurrent data download within a grid computing environment |
US7277985B2 (en) * | 2004-07-13 | 2007-10-02 | International Business Machines Corporation | Method, system and program product for storing downloadable content on a plurality of enterprise storage system (ESS) cells |
US7613787B2 (en) | 2004-09-24 | 2009-11-03 | Microsoft Corporation | Efficient algorithm for finding candidate objects for remote differential compression |
US8903760B2 (en) * | 2004-11-12 | 2014-12-02 | International Business Machines Corporation | Method and system for information workflows |
US20070094348A1 (en) * | 2005-01-07 | 2007-04-26 | Microsoft Corporation | BITS/RDC integration and BITS enhancements |
US8073926B2 (en) * | 2005-01-07 | 2011-12-06 | Microsoft Corporation | Virtual machine image server |
US7849462B2 (en) * | 2005-01-07 | 2010-12-07 | Microsoft Corporation | Image server |
US8602860B2 (en) * | 2005-02-14 | 2013-12-10 | Cork Group Trading Ltd. | Multi-play poker game with pool hand |
US8156428B1 (en) * | 2005-02-25 | 2012-04-10 | Adobe Systems Incorporated | Method and apparatus for merging digital content |
US7676554B1 (en) | 2005-09-15 | 2010-03-09 | Juniper Networks, Inc. | Network acceleration device having persistent in-memory cache |
US7979509B1 (en) | 2005-09-15 | 2011-07-12 | Juniper Networks, Inc. | Clustered network acceleration devices having shared cache |
US7644108B1 (en) | 2005-09-15 | 2010-01-05 | Juniper Networks, Inc. | Network acceleration device cache supporting multiple historical versions of content |
US8214827B2 (en) * | 2005-12-05 | 2012-07-03 | Flash Networks, Ltd | Method and system for improving user confidence and experience in content purchasing via a service provider premises |
US7651593B2 (en) | 2005-12-19 | 2010-01-26 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8655850B2 (en) | 2005-12-19 | 2014-02-18 | Commvault Systems, Inc. | Systems and methods for resynchronizing information |
US7661028B2 (en) | 2005-12-19 | 2010-02-09 | Commvault Systems, Inc. | Rolling cache configuration for a data replication system |
US7606844B2 (en) | 2005-12-19 | 2009-10-20 | Commvault Systems, Inc. | System and method for performing replication copy storage operations |
US7931191B2 (en) * | 2006-01-18 | 2011-04-26 | Dell Products L.P. | Post factory dynamic application selection |
US20070211674A1 (en) | 2006-03-09 | 2007-09-13 | Ragnar Karlberg Lars J | Auto continuation/discontinuation of data download and upload when entering/leaving a network |
US8726242B2 (en) | 2006-07-27 | 2014-05-13 | Commvault Systems, Inc. | Systems and methods for continuous data replication |
US20080115152A1 (en) * | 2006-11-15 | 2008-05-15 | Bharat Welingkar | Server-controlled heartbeats |
WO2008065665A2 (en) * | 2006-11-30 | 2008-06-05 | Speedbit Ltd. | Accelerated multimedia file download and playback |
US8312323B2 (en) | 2006-12-22 | 2012-11-13 | Commvault Systems, Inc. | Systems and methods for remote monitoring in a computer network and reporting a failed migration operation without accessing the data being moved |
US8055902B2 (en) * | 2007-01-12 | 2011-11-08 | International Business Machines Corporation | Method, system, and computer program product for data upload in a computing system |
US8429286B2 (en) * | 2007-06-28 | 2013-04-23 | Apple Inc. | Methods and systems for rapid data acquisition over the internet |
US20090064129A1 (en) * | 2007-08-31 | 2009-03-05 | Mediatek Inc. | Suspend and resume mechanisms on a flash memory |
US8806037B1 (en) | 2008-02-29 | 2014-08-12 | Netapp, Inc. | Remote support automation for a storage server |
US7913115B1 (en) * | 2008-04-30 | 2011-03-22 | Netapp, Inc. | Core file transfer |
US8086909B1 (en) | 2008-11-05 | 2011-12-27 | Network Appliance, Inc. | Automatic core file upload |
US8204859B2 (en) | 2008-12-10 | 2012-06-19 | Commvault Systems, Inc. | Systems and methods for managing replicated database data |
US9495382B2 (en) | 2008-12-10 | 2016-11-15 | Commvault Systems, Inc. | Systems and methods for performing discrete data replication |
US20100285885A1 (en) * | 2009-05-07 | 2010-11-11 | Microsoft Corporation | Massively multiplayer game message scheduling |
US9450804B2 (en) | 2009-09-03 | 2016-09-20 | At&T Intellectual Property I, L.P. | Anycast aware transport for content distribution networks |
US8504517B2 (en) | 2010-03-29 | 2013-08-06 | Commvault Systems, Inc. | Systems and methods for selective data replication |
US8504515B2 (en) | 2010-03-30 | 2013-08-06 | Commvault Systems, Inc. | Stubbing systems and methods in a data replication environment |
US9021198B1 (en) | 2011-01-20 | 2015-04-28 | Commvault Systems, Inc. | System and method for sharing SAN storage |
KR101849782B1 (en) * | 2011-10-07 | 2018-04-18 | 한국전자통신연구원 | Apparatus and method of searching data for post-processing of satellite telemetry data |
US8869041B2 (en) | 2011-11-11 | 2014-10-21 | Apollo Education Group, Inc. | Dynamic and local management of hierarchical discussion thread data |
US8966404B2 (en) | 2011-11-11 | 2015-02-24 | Apollo Education Group, Inc. | Hierarchy-indicating graphical user interface for discussion threads |
US20130125061A1 (en) * | 2011-11-11 | 2013-05-16 | Jongwoo LEE | Efficient Navigation Of Hierarchical Data Displayed In A Graphical User Interface |
US9471578B2 (en) | 2012-03-07 | 2016-10-18 | Commvault Systems, Inc. | Data storage system utilizing proxy device for storage operations |
US9298715B2 (en) | 2012-03-07 | 2016-03-29 | Commvault Systems, Inc. | Data storage system utilizing proxy device for storage operations |
US9342537B2 (en) | 2012-04-23 | 2016-05-17 | Commvault Systems, Inc. | Integrated snapshot interface for a data storage system |
US9306860B2 (en) * | 2012-10-18 | 2016-04-05 | Giraffic Technologies Ltd. | Congestion control method for dynamically maximizing communication link throughout |
US9886346B2 (en) | 2013-01-11 | 2018-02-06 | Commvault Systems, Inc. | Single snapshot for multiple agents |
US9430491B2 (en) | 2013-01-11 | 2016-08-30 | Commvault Systems, Inc. | Request-based data synchronization management |
US9495251B2 (en) | 2014-01-24 | 2016-11-15 | Commvault Systems, Inc. | Snapshot readiness checking and reporting |
US9753812B2 (en) | 2014-01-24 | 2017-09-05 | Commvault Systems, Inc. | Generating mapping information for single snapshot for multiple applications |
US9632874B2 (en) | 2014-01-24 | 2017-04-25 | Commvault Systems, Inc. | Database application backup in single snapshot for multiple applications |
US9639426B2 (en) | 2014-01-24 | 2017-05-02 | Commvault Systems, Inc. | Single snapshot for multiple applications |
US9747167B2 (en) * | 2014-02-27 | 2017-08-29 | Nice Ltd. | Persistency free architecture |
LU92417B1 (en) * | 2014-04-01 | 2015-10-02 | Gt Sat Internat Sarl | ODU Controlling system in single-cable installation environment |
US20150370409A1 (en) * | 2014-06-18 | 2015-12-24 | International Business Machines Corporation | Disambiguation of touch-based gestures |
US9774672B2 (en) | 2014-09-03 | 2017-09-26 | Commvault Systems, Inc. | Consolidated processing of storage-array commands by a snapshot-control media agent |
US10042716B2 (en) | 2014-09-03 | 2018-08-07 | Commvault Systems, Inc. | Consolidated processing of storage-array commands using a forwarder media agent in conjunction with a snapshot-control media agent |
US9648105B2 (en) | 2014-11-14 | 2017-05-09 | Commvault Systems, Inc. | Unified snapshot storage management, using an enhanced storage manager and enhanced media agents |
US9448731B2 (en) | 2014-11-14 | 2016-09-20 | Commvault Systems, Inc. | Unified snapshot storage management |
US9904481B2 (en) | 2015-01-23 | 2018-02-27 | Commvault Systems, Inc. | Scalable auxiliary copy processing in a storage management system using media agent resources |
US9898213B2 (en) | 2015-01-23 | 2018-02-20 | Commvault Systems, Inc. | Scalable auxiliary copy processing using media agent resources |
US10033794B2 (en) * | 2015-07-17 | 2018-07-24 | Bio-Rad Laboratories, Inc. | Network transfer of large files in unstable network environments |
US10503753B2 (en) | 2016-03-10 | 2019-12-10 | Commvault Systems, Inc. | Snapshot replication operations based on incremental block change tracking |
US10108412B2 (en) | 2016-03-30 | 2018-10-23 | Square, Inc. | Blocking and non-blocking firmware update |
US11010765B2 (en) | 2016-06-29 | 2021-05-18 | Square, Inc. | Preliminary acquisition of payment information |
US10817869B2 (en) | 2016-06-29 | 2020-10-27 | Square, Inc. | Preliminary enablement of transaction processing circuitry |
US11010261B2 (en) | 2017-03-31 | 2021-05-18 | Commvault Systems, Inc. | Dynamically allocating streams during restoration of data |
JP6915399B2 (en) * | 2017-06-16 | 2021-08-04 | 富士フイルムビジネスイノベーション株式会社 | Information processing equipment and information processing programs |
US10732885B2 (en) | 2018-02-14 | 2020-08-04 | Commvault Systems, Inc. | Block-level live browsing and private writable snapshots using an ISCSI server |
US10990969B2 (en) | 2018-12-21 | 2021-04-27 | Square, Inc. | Point of sale (POS) systems and methods for dynamically processing payment data based on payment reader capability |
US10762196B2 (en) | 2018-12-21 | 2020-09-01 | Square, Inc. | Point of sale (POS) systems and methods with dynamic kernel selection |
US11049095B2 (en) | 2018-12-21 | 2021-06-29 | Square, Inc. | Point of sale (POS) systems and methods with dynamic kernel selection |
US11042318B2 (en) | 2019-07-29 | 2021-06-22 | Commvault Systems, Inc. | Block-level data replication |
KR20210035636A (en) * | 2019-09-24 | 2021-04-01 | 엘지전자 주식회사 | Server |
CN113612735B (en) * | 2021-07-15 | 2022-09-02 | 中国联合网络通信集团有限公司 | Secure storage system |
CN114024950B (en) * | 2021-09-13 | 2023-06-30 | 福建新大陆通信科技股份有限公司 | Big data transmission method and system for electronic equipment |
US11809285B2 (en) | 2022-02-09 | 2023-11-07 | Commvault Systems, Inc. | Protecting a management database of a data storage management system to meet a recovery point objective (RPO) |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US555083A (en) * | 1896-02-25 | flint | ||
US4712214A (en) * | 1986-01-10 | 1987-12-08 | International Business Machines Corporation | Protocol for handling transmission errors over asynchronous communication lines |
US5495610A (en) * | 1989-11-30 | 1996-02-27 | Seer Technologies, Inc. | Software distribution system to build and distribute a software release |
US5673252A (en) * | 1990-02-15 | 1997-09-30 | Itron, Inc. | Communications protocol for remote data generating stations |
US5267235A (en) * | 1992-05-21 | 1993-11-30 | Digital Equipment Corporation | Method and apparatus for resource arbitration |
US5396613A (en) * | 1992-11-05 | 1995-03-07 | University Of Utah Research Foundation | Method and system for error recovery for cascaded servers |
US5506958A (en) * | 1993-02-10 | 1996-04-09 | Conner Peripherals, Inc. | Error detection for parallel data transfer between a processor and a peripheral device by comparing regisgers storing a sum of values in bytes of data transferred |
DE69527623T2 (en) * | 1994-05-19 | 2003-03-13 | British Telecomm | File transfer mechanism |
US5583563A (en) * | 1995-01-12 | 1996-12-10 | Us West Marketing Resources Group, Inc. | Method and system for delivering an application in an interactive television network |
US5553083B1 (en) * | 1995-01-19 | 2000-05-16 | Starburst Comm Corp | Method for quickly and reliably transmitting frames of data over communications links |
JP2792454B2 (en) * | 1995-02-09 | 1998-09-03 | 日本電気株式会社 | Video search system |
US5699513A (en) * | 1995-03-31 | 1997-12-16 | Motorola, Inc. | Method for secure network access via message intercept |
US5696898A (en) * | 1995-06-06 | 1997-12-09 | Lucent Technologies Inc. | System and method for database access control |
US5638299A (en) * | 1995-06-22 | 1997-06-10 | Miller; Keith | Light weight, self-contained programmable data-acquisition system |
US6049671A (en) * | 1996-04-18 | 2000-04-11 | Microsoft Corporation | Method for identifying and obtaining computer software from a network computer |
US5721824A (en) * | 1996-04-19 | 1998-02-24 | Sun Microsystems, Inc. | Multiple-package installation with package dependencies |
US5949419A (en) * | 1996-05-13 | 1999-09-07 | Domine; Robert M | Web browser detection and default home page modification device |
US5974461A (en) * | 1996-06-03 | 1999-10-26 | Webtv Networks, Inc. | Method for automatically regenerating information at a client system in the event of power or communication disruption between the client system and the server |
US5835724A (en) * | 1996-07-03 | 1998-11-10 | Electronic Data Systems Corporation | System and method for communication information using the internet that receives and maintains information concerning the client and generates and conveys the session data to the client |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US6098180A (en) * | 1997-02-18 | 2000-08-01 | E-Parcel, Llc | Robust delivery system |
US6049892C1 (en) * | 1997-02-24 | 2002-06-04 | Ethos Software Corp | Process and apparatus for downloading data from a server computer to a client computer |
-
1997
- 1997-02-24 US US08804902 patent/US6049892C1/en not_active Expired - Fee Related
-
1998
- 1998-02-24 JP JP53858198A patent/JP2002510412A/en active Pending
- 1998-02-24 WO PCT/US1998/003534 patent/WO1998039707A1/en not_active Application Discontinuation
- 1998-02-24 EP EP98907595A patent/EP1019816A4/en not_active Withdrawn
- 1998-02-24 AU AU63361/98A patent/AU742817B2/en not_active Ceased
- 1998-02-24 CA CA002281672A patent/CA2281672A1/en not_active Abandoned
-
2000
- 2000-04-03 US US09/541,184 patent/US6381709B1/en not_active Expired - Fee Related
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11169899B2 (en) * | 2019-04-15 | 2021-11-09 | Toyota Motor Engineering & Manufacturing North America, Inc. | Mitigating data offsets for machine learning |
Also Published As
Publication number | Publication date |
---|---|
EP1019816A1 (en) | 2000-07-19 |
AU742817B2 (en) | 2002-01-10 |
EP1019816A4 (en) | 2005-08-03 |
WO1998039707A1 (en) | 1998-09-11 |
JP2002510412A (en) | 2002-04-02 |
US6381709B1 (en) | 2002-04-30 |
US6049892C1 (en) | 2002-06-04 |
AU6336198A (en) | 1998-09-22 |
US6049892A (en) | 2000-04-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU742817B2 (en) | Process and apparatus for downloading data from a server computer to a client computer | |
EP1248984B1 (en) | Methods and apparatus for downloading a file from a server | |
US6430707B1 (en) | Source-level debugging of client dump image in a computer network | |
EP0971519A1 (en) | Computer data transfer | |
US20040199809A1 (en) | System and method for downloading files over a network with real time verification | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | Configuring XRemote | |
Cisco | XRemote Configuration and Management | |
Cisco | XRemote Configuration and Management | |
Cisco | XRemote Configuration and Management | |
Cisco | XRemote Configuration and Management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |