Method and apparatus for facilitating data transfers between arbitrary components
First Claim
1. A method for transferring data between system components, comprising:
- receiving a transfer session object at a data sink component through a universal data transfer interface, wherein the transfer session object contains mobile code which includes executable content with a functionality that implements a source-specific data transfer protocol for communicating with a data source component;
executing the mobile code; and
retrieving data from the data source component through the transfer session object, whereby the data sink component can retrieve data from the data source component without having to be preconfigured with the source-specific data transfer protocol for communicating with the data source component;
wherein if the data sink component does not indicate continued proof of interest for a predetermined amount of time, the data source component and the data sink component automatically clean up their state, without the need for any ongoing communication;
wherein prior to obtaining the transfer session object from the data source component, a client;
performs a discovery operation to discover available components in the system;
inspects the available components to determine which universal interfaces are supported by each available component;
selects the data source component from the available components; and
selects the data sink component from the available components.
7 Assignments
0 Petitions
Accused Products
Abstract
One embodiment of the present invention provides a system that facilitates transferring data between system components. During operation, the system receives a transfer session object at a data sink component through a universal data transfer interface, wherein the transfer session object contains mobile code that implements a source-specific data transfer protocol for communicating with a data source component. Next, the system retrieves data from the data source component through the transfer session object. In this way, the data sink component can retrieve data from the data source component without having to be preconfigured with the source-specific data transfer protocol for communicating with the data source component.
8 Citations
31 Claims
-
1. A method for transferring data between system components, comprising:
-
receiving a transfer session object at a data sink component through a universal data transfer interface, wherein the transfer session object contains mobile code which includes executable content with a functionality that implements a source-specific data transfer protocol for communicating with a data source component; executing the mobile code; and retrieving data from the data source component through the transfer session object, whereby the data sink component can retrieve data from the data source component without having to be preconfigured with the source-specific data transfer protocol for communicating with the data source component; wherein if the data sink component does not indicate continued proof of interest for a predetermined amount of time, the data source component and the data sink component automatically clean up their state, without the need for any ongoing communication; wherein prior to obtaining the transfer session object from the data source component, a client; performs a discovery operation to discover available components in the system; inspects the available components to determine which universal interfaces are supported by each available component; selects the data source component from the available components; and selects the data sink component from the available components. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for transferring data between system components, the method comprising:
-
receiving a transfer session object at a data sink component through a universal data transfer interface, wherein the transfer session object contains mobile code which includes executable content with a functionality that implements a source-specific data transfer protocol for communicating with a data source component; executing the mobile code; and retrieving data from the data source component through the transfer session object, whereby the data sink component can retrieve data from the data source component without having to be preconfigured with the source-specific data transfer protocol for communicating with the data source component; wherein if the data sink component does not indicate continued proof of interest for a predetermined amount of time, the data source component and the data sink component automatically clean up their state, without the need for any ongoing communication.; wherein prior to obtaining the transfer session object from the data source component, a client; performs a discovery operation to discover available components in the system; inspects the available components to determine which universal interfaces are supported by each available component; selects the data source component from the available components; and selects the data sink component from the available components. - View Dependent Claims (16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28)
-
-
29. An apparatus for transferring data between system components, comprising:
-
a data sink component configured to receive a transfer session object through a universal data transfer interface, wherein the transfer session object contains mobile code which includes executable content with a functionality that implements a source-specific data transfer protocol for communicating with a data source component; and wherein the data sink component is additionally configured to execute the mobile code to retrieve data from the data source component through the transfer session object, whereby the data sink component can retrieve data from the data source component without having to be preconfigured with the source-specific data transfer protocol for communicating with the data source component;
wherein if the data sink component does not indicate continued proof of interest for a predetermined amount of time, the data source component and the data sink component automatically clean up their state, without the need for any ongoing communication; and
wherein the apparatus further comprises a client which prior to obtaining the transfer session object from the data source component is configured to;perform a discovery operation to discover available components in the system; inspect the available components to determine which universal interfaces are supported by each available component; selects the data source component from the available components; and selects the data sink component from the available components. - View Dependent Claims (30, 31)
-
Specification