Browse Prior Art Database

RDM 4.1 D-Server HTTP File Transfer Algorithm

IP.com Disclosure Number: IPCOM000021511D
Original Publication Date: 2004-Jan-21
Included in the Prior Art Database: 2004-Jan-21
Document File: 1 page(s) / 45K

Publishing Venue

IBM

Abstract

Two endpoints communicate by alternatively sending the URL (Uniform Resource Locator) (pointing to the message file) embedded in a HTTP (Hyper-Text Transport Protocol) HEAD request from sender to the receiver.

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

Page 1 of 1

THIS COPY WAS MADE FROM AN INTERNAL IBM DOCUMENT AND NOT FROM THE PUBLISHED BOOK

BEA820030031 Bryan W Butler/San Jose/IBM Yih-Herng Chuang

RDM 4.1 D-Server HTTP File Transfer Algorithm

Deployment Servers (D-Server) are applied to a Wide Area Network as relays to different local area networks. A Master D-Server (MDS) is installed at the center node of the D-Server star topology, and Remote D-Server (RDS) is installed on each network to serve the clients connecting to the network. All these RDS's communicate with MDS by HTTP. Both MDS and RDS can be HTTP Sender and HTTP Receiver, depending on who initiates the request. The one initiating HTTP request is the HTTP Sender and the other endpoint becomes the HTTP Receiver. MDS and RDS may switch role as Sender and Receiver as needed. This method requires only a light weight HTTP Server, and an invented simple proprietary protocol to enable the message passing through basic HEAD and GET of HTTP 1.0 commands.

Scenario: Sender sends message Msg_A to Receiver:
1. Sender creates a Msg_A object
2. Sender serialize Msg_A object into file_A located under HTTP document root on hard drive.
3. Sender creates a Command Bean object including the following information:
a) The full URL of file_A including sender's IP address and HTTP server port number.
b) Size of file_A
c) Checksum of file_A
4. Sender converts the Command Bean object into text lines and has them embedded into HTTP request header.
5. Sender sends HTTP request to receiver by...