US6401099B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Asynchronous binding of named objects
Assignee: Microsoft Technology Licensing LLC
•
Filing: 1996-12-06
•
Granted: 2002-06-04
•
Expires: 2016-12-06
Abstract
Abstract An object-oriented framework unifies retrieval and browsing of data locally and from remote computer networks. The framework includes a class of monikers that operate on behalf of a client program to asynchronously bind or retrieve data referenced by a name without blocking execution of the client. This allows the client to provide responsive user interaction including when remotely retrieving data.
Inventors
- 👤 Srinivasa R. Koppolu
- 👤 Johann Posch
- 👤 Victor Stone
- 👤 Antony S. Williams
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-03 04:31
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/543; Y; Y10; Y10S; Y10S707/00; Y10S707/99941; Y10S707/99944; Y10S707/99945
Claims Analysis
Total Claims: 81
Claim 1
Independent Claim
72 words
An object-oriented framework for providing asynchronous retrieval of data from a storage site for a client, wherein the client comprises plural instructions for executing, the object-oriented framework comprising: a naming object having a reference to the data; and a binding function callable from the client to initiate asynchronous retrieval of the data from the storage site, the client continuing instruction execution independently of the retrieval of the data from the storage site.
Claim 2
Dependent Claim
72 words
An object-oriented framework for providing asynchronous retrieval of data from a storage site for a client, wherein the client comprises plural instructions for executing, the object-oriented framework comprising: a naming object having a reference to the data; and a binding function callable from the client to initiate asynchronous retrieval of the data from the storage site, the client continuing instruction execution independently of the retrieval of the data from the storage site.
Claim 3
Dependent Claim
53 words
The object-oriented framework of claim 1 comprising: a bind context object for the client to register a call back interface callable from the naming object, wherein the call back interface exposes one or more functions supported by the client for the naming object to invoke in order to initiate communication with the client.
Claim 4
Dependent Claim
25 words
The object-oriented framework of claim 2 wherein the call back interface exposes a function operable to notify the client about progress of the data retrieval.
Claim 5
Dependent Claim
38 words
The object-oriented framework of claim 2 wherein the call back interface exposes a function for the naming object to get parameters relating to the data retrieval from the client, whereby the client controls aspects of the data retrieval.
Claim 6
Dependent Claim
30 words
The object-oriented framework of claim 1 wherein the naming object operates in a data pull mode to retrieve the data from the storage site when the client reads the data.
Claim 7
Dependent Claim
35 words
The object-oriented framework of claim 1 wherein the naming object operates in a data push mode to retrieve the data from the storage site and notify the client when the data is available for reading.
Claim 8
Dependent Claim
54 words
The object-oriented framework of claim 1 comprising: an asynchronous storage object provided by the naming object for storing the data retrieved from the storage site, and for allowing access by the client to a part of the data already retrieved from the storage site during the data retrieval before the data retrieval is completed.
Claim 9
Dependent Claim
80 words
The object-oriented framework of claim 7 wherein the asynchronous storage object has a non-blocking mode in which execution of the client is not blocked when accessing a part of the data not yet retrieved from the storage site, and a blocking mode in which execution of the client is blocked when accessing the part of the data not yet retrieved from the storage site, the asynchronous storage object operating in the blocking or non-blocking mode as set by the client.
Claim 10
Dependent Claim
27 words
The object-oriented framework of claim 1 wherein the naming object is operative to perform asynchronous or synchronous data retrieval depending on a flag set by the client.
Claim 11
Dependent Claim
22 words
The object-oriented framework of claim 1 comprising: a function provided by the naming object for the client to interrupt the data retrieval.
Claim 12
Dependent Claim
32 words
The object-oriented framework of claim 1 comprising: a binding interface provided by the naming object and having functions callable from the client to cause the data retrieval to abort, suspend, and resume.
Claim 13
Dependent Claim
44 words
The object-oriented framework of claim 1 comprising: a plurality of other naming objects for retrieving data from storage sites; the naming object performing the data retrieval according to a priority set by the client relative to data retrievals performed by the other naming objects.
Claim 14
Dependent Claim
38 words
The object-oriented framework of claim 1 wherein the reference is a resource identifier of data residing on a remote computer network, the naming object operating to asynchronously retrieve the data for the client from the remote computer network.
Claim 15
Dependent Claim
41 words
The object-oriented framework of claim 13 in which the naming object obtains information of any preferred formats for the data from the client, and retrieves the data from the remote computer network in an available one of the preferred data formats.
Claim 16
Dependent Claim
34 words
The object-oriented framework of claim 13 in which the naming object performs media type negotiation between the client and the remote computer network of a format in which the naming object retrieves the data.
Claim 17
Dependent Claim
64 words
The object-oriented framework of claim 13 comprising: a bind context object for the client to register an interface provided by the client having a format enumeration function callable from the naming object for the client to request any preferred formats for the data, the naming object operating to retrieve the data in an available one of the preferred formats from the remote computer network.
Claim 18
Dependent Claim
46 words
The object-oriented framework of claim 13 comprising: a bind context object for the client to register an interface provided by the client having an authentication function callable from the naming object for the client to provide authentication of the data retrieval from the remote computer network.
Claim 19
Dependent Claim
39 words
The object-oriented framework of claim 13 in which the naming object performs parameter negotiation between the client and the remote computer network of a transport protocol with which the naming object retrieves the data from the remote computer network.
Claim 20
Dependent Claim
48 words
The object-oriented framework of claim 13 comprising: a bind context object for the client to register an interface provided by the client having functions callable from the naming object for the client to negotiate parameters of a transport protocol for retrieving the data from the remote computer network.
Claim 21
Independent Claim
99 words
A method of retrieving data in a computer system, comprising: providing an interface of a naming object having a reference designating stored data to a client application, wherein the client application comprises plural instructions for executing, the interface exposing a binding function of the naming object operative to perform a binding operation on the stored data; and on a call from the client application to the binding function, initiating binding the stored data as a background process while returning execution to the client application, the client application continuing instruction execution independently of the binding operation on the stored data.
Claim 22
Independent Claim
99 words
A method of retrieving data in a computer system, comprising: providing an interface of a naming object having a reference designating stored data to a client application, wherein the client application comprises plural instructions for executing, the interface exposing a binding function of the naming object operative to perform a binding operation on the stored data; and on a call from the client application to the binding function, initiating binding the stored data as a background process while returning execution to the client application, the client application continuing instruction execution independently of the binding operation on the stored data.
Claim 23
Dependent Claim
54 words
The method of claim 20 comprising receiving a call back interface on the client application, the call back interface exposing at least one function supported by the client application callable from the naming object for sending notifications relating to the binding operation of the stored data from the naming object to the client application.
Claim 24
Dependent Claim
36 words
The method of claim 21 comprising: repeatedly calling a progress notification function of the call back interface during the binding operation to provide an indication of the progress of the binding operation to the client application.
Claim 25
Dependent Claim
47 words
The method of claim 21 comprising: calling a data available notification function of the call back interface to notify the client application at a time before the binding operation is completed that a retrieved part of the stored data is available for the client application to access.
Claim 26
Dependent Claim
34 words
The method of claim 21 comprising: calling a stop binding notification function of the call back interface to notify the client application of a status of the binding operation at ending the binding operation.
Claim 27
Dependent Claim
41 words
The method of claim 20 comprising: passing a binding interface by the naming object to the client application, the binding interface exposing an abort function; and terminating the binding operation upon a call from the client application to the abort function.
Claim 28
Dependent Claim
60 words
The method of claim 20 comprising: passing a binding interface by the naming object to the client application, the binding interface exposing a suspend function and a resume function; suspending the binding operation upon a call from the client application to the suspend function; and resuming the binding operation upon a call from the client application to the resume function.
Claim 29
Dependent Claim
55 words
The method of claim 20 comprising: passing a binding interface by the naming object to the client application, the binding interface exposing a priority setting function; and establishing a priority of a thread for executing the binding operation according to a value passed from the client application in a call to the priority setting function.
Claim 30
Dependent Claim
94 words
The method of claim 20 comprising: providing an interface of a bind context object to the client application, the bind context object operative to register a call back interface of the client application, wherein the call back interface exposes functions supported by the client application callable from the naming object to initiate communication with the client application; receiving the interface of the bind context object in the client application's call to the binding function; and calling functions on the call back interface to provide notifications to the client application relating to the binding operation.
Claim 31
Dependent Claim
71 words
The method of claim 20 comprising, in the binding operation: creating a storage object having an interface which exposes a read function for reading data in the storage object; passing the interface of the storage object to the client application; and retrieving the stored data into the storage object by the background process, whereby the client application has access to the stored data in the storage object during the binding operation.
Claim 32
Dependent Claim
38 words
The method of claim 29 comprising: returning a retrieval pending error notification to the client application when the client application calls the read function to access the stored data which is not yet retrieved into the storage object.
Claim 33
Independent Claim
166 words
A method of creating a moniker object to retrieve data referenced by a name, the name having a prefix portion indicative of a transport protocol followed by a colon character, the method comprising: registering a program identifier indicative of the transport protocol in association with a class identifier in a registry database, the class identifier being associated with a server application which supports a class of transport protocol object, objects of said class being operative to communicate using the transport protocol to retrieve named data and having a name parsing function operative to create monikers from names using the transport protocol; parsing the prefix portion up to the colon character from the name; searching the program identifiers in the registry for a match to the prefix portion; on matching the prefix portion to the program identifier indicative indicative of the transport protocol, instantiating a transport protocol object of said class and calling the name parsing function on the name so as to create the moniker object.
Claim 34
Independent Claim
166 words
A method of creating a moniker object to retrieve data referenced by a name, the name having a prefix portion indicative of a transport protocol followed by a colon character, the method comprising: registering a program identifier indicative of the transport protocol in association with a class identifier in a registry database, the class identifier being associated with a server application which supports a class of transport protocol object, objects of said class being operative to communicate using the transport protocol to retrieve named data and having a name parsing function operative to create monikers from names using the transport protocol; parsing the prefix portion up to the colon character from the name; searching the program identifiers in the registry for a match to the prefix portion; on matching the prefix portion to the program identifier indicative indicative of the transport protocol, instantiating a transport protocol object of said class and calling the name parsing function on the name so as to create the moniker object.
Claim 35
Dependent Claim
142 words
A storage medium having instructions therein for causing a computer to perform a data retrieval method comprising the steps of: creating a bind context object for storing information relating to a binding operation; registering a call back interface supported by a client application with the bind context object, wherein the call back interface exposes functions supported by the client application callable from the naming object to initiate communication with the client application, and wherein the client application comprises plural instructions for executing; creating a moniker object containing a name that references stored data and having a bind function; initiating a binding operation in the bind function which executes asynchronously of the client application, the client application continuing instruction execution independently of the binding operation; and providing notifications to the client application relating to the binding operation's status with the call back interface.
Claim 36
Dependent Claim
142 words
A storage medium having instructions therein for causing a computer to perform a data retrieval method comprising the steps of: creating a bind context object for storing information relating to a binding operation; registering a call back interface supported by a client application with the bind context object, wherein the call back interface exposes functions supported by the client application callable from the naming object to initiate communication with the client application, and wherein the client application comprises plural instructions for executing; creating a moniker object containing a name that references stored data and having a bind function; initiating a binding operation in the bind function which executes asynchronously of the client application, the client application continuing instruction execution independently of the binding operation; and providing notifications to the client application relating to the binding operation's status with the call back interface.
Claim 37
Dependent Claim
47 words
The storage medium of claim 32 wherein the data retrieval method further comprises: returning a bind interface from the moniker object to the client application, the bind interface having functions for at least one of aborting, suspending, resuming, and setting an execution priority of the binding operation.
Claim 38
Dependent Claim
38 words
The storage medium of claim 32 wherein the step of providing notifications in the method comprises: repeatedly providing progress notifications during the binding operation to the client application indicative of which proportion of the binding operation is complete.
Claim 39
Dependent Claim
46 words
The storage medium of claim 32 wherein the method comprises: registering information in the bind context of any media types acceptable to the client application for retrieving the stored data; and retrieving the stored data in the binding operation in one of said acceptable media types.
Claim 40
Dependent Claim
138 words
In a computer system having at least one computer, a moniker object comprising: a name element for storing a name that identifies data stored in the computer system; an interface structure through which a client invokes method elements of the moniker object via synchronous calls that suspend instruction execution of the client pending return from the synchronous calls; and a bind method element invoked by the client through such a synchronous call using the interface structure, the invoked bind method element operating to commence a retrieval operation to retrieve the data identified by the name and to return from said synchronous call during the retrieval operation, the return from said synchronous call permitting continued instruction execution of the client independent of the retrieval operation, whereby the continued instruction execution of the client occurs asynchronously of the retrieval operation.
Claim 41
Dependent Claim
138 words
In a computer system having at least one computer, a moniker object comprising: a name element for storing a name that identifies data stored in the computer system; an interface structure through which a client invokes method elements of the moniker object via synchronous calls that suspend instruction execution of the client pending return from the synchronous calls; and a bind method element invoked by the client through such a synchronous call using the interface structure, the invoked bind method element operating to commence a retrieval operation to retrieve the data identified by the name and to return from said synchronous call during the retrieval operation, the return from said synchronous call permitting continued instruction execution of the client independent of the retrieval operation, whereby the continued instruction execution of the client occurs asynchronously of the retrieval operation.
Claim 42
Dependent Claim
55 words
The moniker object of claim 36 in combination with a bind context object for the client to register a call back interface callable from the moniker object, wherein the call back interface exposes one or more functions supported by the client for the moniker object to invoke in order to initiate communication with the client.
Claim 43
Dependent Claim
46 words
The moniker object of claim 36 in combination with an asynchronous storage object provided by the moniker object for storing retrieved data, and for allowing access by the client to a part of the retrieved data during the retrieval operation before the retrieval operation is completed.
Claim 44
Dependent Claim
39 words
The moniker object of claim 36 further comprising: a flow control element invoked by the client through such a synchronous call using the interface structure, the invoked flow control element operating to affect the execution of the retrieval operation.
Claim 45
Dependent Claim
45 words
The moniker object and bind context object of claim 38 wherein the moniker object obtains information of any preferred data formats from the client, and retrieves the data from a remote computer in the computer system in an available one of the preferred data formats.
Claim 46
Dependent Claim
17 words
The object-oriented framework of claim 1 wherein the data retrieval and the client instruction execution occur concurrently.
Claim 47
Dependent Claim
15 words
The object-oriented framework of claim 1 wherein the data retrieval occurs as a background process.
Claim 48
Dependent Claim
114 words
An object-oriented framework for providing asynchronous retrieval of data from a storage site for a client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program further includes a name that references a named item, the object-oriented framework comprising: association data defining an association of the name to the named item; a system object that exposes a programming interface to the client application program, wherein the programming interface includes a retrieval function, wherein the client application program initiates asynchronous retrieval of data for the named item through the retrieval function, and wherein the client application program continues instruction execution independently of the asynchronous retrieval of data.
Claim 49
Dependent Claim
114 words
An object-oriented framework for providing asynchronous retrieval of data from a storage site for a client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program further includes a name that references a named item, the object-oriented framework comprising: association data defining an association of the name to the named item; a system object that exposes a programming interface to the client application program, wherein the programming interface includes a retrieval function, wherein the client application program initiates asynchronous retrieval of data for the named item through the retrieval function, and wherein the client application program continues instruction execution independently of the asynchronous retrieval of data.
Claim 50
Dependent Claim
38 words
The object-oriented framework of claim 43 wherein the programming interface returns to the client application program a reference to a control interface, and wherein the client application program controls the asynchronous retrieval of data through the control interface.
Claim 51
Dependent Claim
14 words
The object-oriented framework of claim 43 wherein the name reflects a hierarchical name space.
Claim 52
Dependent Claim
28 words
The object-oriented framework of claim 43 wherein the name indicates a transport protocol, and wherein the initiated asynchronous retrieval of data occurs according to the indicated transport protocol.
Claim 53
Dependent Claim
18 words
The object-oriented framework of claim 43 wherein the system object places the asynchronously retrieved data in persistent storage.
Claim 54
Dependent Claim
22 words
The object-oriented framework of claim 43 wherein the system object places the asynchronously retrieved data in an object associated with the name.
Claim 55
Dependent Claim
119 words
An object-oriented framework for providing asynchronous retrieval of data from a storage site for client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program furthr includes a name that references a named item, the object-oriented framework comprising: association data defining an association of the name to the named item, wherein the name further indicates a transport protocol for retrieving data for the named item; a retrieval object that implements the transport protocol indicated by the name, wherein the retrieval object handles asynchronous retrieval of data for the named item at the transport protocol level, and wherein the client application program continues instruction execution independently of the asynchronous retrieval of data.
Claim 56
Dependent Claim
119 words
An object-oriented framework for providing asynchronous retrieval of data from a storage site for client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program furthr includes a name that references a named item, the object-oriented framework comprising: association data defining an association of the name to the named item, wherein the name further indicates a transport protocol for retrieving data for the named item; a retrieval object that implements the transport protocol indicated by the name, wherein the retrieval object handles asynchronous retrieval of data for the named item at the transport protocol level, and wherein the client application program continues instruction execution independently of the asynchronous retrieval of data.
Claim 57
Dependent Claim
26 words
The object-oriented framework of claim 49 wherein the retrieval object exposes control interface that includes one or more functions for controlling the asynchronous retrieval of data.
Claim 58
Dependent Claim
18 words
the object-oriented framework of claim 49 wherein a system object encompasses the association data and the retrieval object.
Claim 59
Dependent Claim
15 words
The object-oreiented framework of claim 49 wherein computer storage persistently stores the asynchronously retrieved data.
Claim 60
Dependent Claim
18 words
The object-oriented framework of claim 49 wherein an object associated with the name encapsulates the asynchronously retrieved data.
Claim 61
Independent Claim
95 words
A method of communicating between a client application program and a system object to asynchronously retrieve data stored in a computer system, the method comprising: initiating by client application program an asynchronous retrieval operation of stored data for a named item, wherein the asynchronous data retrieval operation executes as a background process, and wherein the client application program continues execution independently of the asynchronous retrieval operation; and providing a control interface to the client application program, wherein the control interface includes functions for the client application program to call to control the asynchronous retrieval operation.
Claim 62
Independent Claim
95 words
A method of communicating between a client application program and a system object to asynchronously retrieve data stored in a computer system, the method comprising: initiating by client application program an asynchronous retrieval operation of stored data for a named item, wherein the asynchronous data retrieval operation executes as a background process, and wherein the client application program continues execution independently of the asynchronous retrieval operation; and providing a control interface to the client application program, wherein the control interface includes functions for the client application program to call to control the asynchronous retrieval operation.
Claim 63
Dependent Claim
28 words
The method of claim 54 further comprising: on a call from the client application program to an abort function of the control interface, aborting the asynchronous retrieval operation.
Claim 64
Dependent Claim
27 words
The method of claim 54 further comprising: on a call from the client application to a suspend function of the control interface, suspending the asynchronous retrieval operation.
Claim 65
Dependent Claim
15 words
The method of claim 54 further comprising: persistently storing asynchronously retrieved data in computer storage.
Claim 66
Dependent Claim
19 words
The method of claim 54 further comprising: encapsulating asynchronously retrieved data within an object associated with the named item.
Claim 67
Independent Claim
110 words
A method of communicating between a client application program and a system object to asynchronously retrieve data stored in a computer system, wherein the client application program includes a client object, the method comprising: initiating by a client application program an asynchronous retrieval operation of stored data for a named item, wherein the a synchronous data retrieval operation executes as a background process, and wherein the client application program continues execution independently of the asynchronous retrieval operation; and providing a callback interface to the system object, wherein the callback interface includes functions for the system object to call to notify the client object of events concerning the asynchronous retrieval operation.
Claim 68
Independent Claim
110 words
A method of communicating between a client application program and a system object to asynchronously retrieve data stored in a computer system, wherein the client application program includes a client object, the method comprising: initiating by a client application program an asynchronous retrieval operation of stored data for a named item, wherein the a synchronous data retrieval operation executes as a background process, and wherein the client application program continues execution independently of the asynchronous retrieval operation; and providing a callback interface to the system object, wherein the callback interface includes functions for the system object to call to notify the client object of events concerning the asynchronous retrieval operation.
Claim 69
Dependent Claim
29 words
The method of claim 59 comprising: on a call to a completion function of the callback interface, notifying the client object of the completion of the asynchronous retrieval operation.
Claim 70
Dependent Claim
32 words
The method of claim 59 further comprising: on a call to a partial completion function of the callback interface, notifying the client object of the partial completion of the asynchronous retrieval operation.
Claim 71
Dependent Claim
15 words
The method of claim 59 further comprising: placing asynchronously retrieved data in persistent computer storage.
Claim 72
Dependent Claim
19 words
The method of claim 59 further comprising: placing asynchronously retrieved data in an object associated with the named item.
Claim 73
Dependent Claim
159 words
An object-oriented framework for providing asynchronous retrieval of data for a named item for a client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program further includes a name that references the named item, the object-oriented framework comprising: a name parsing interface accessible to the client application program and operating to parse a name passed from the client application program in a request issued by the client application program to the interface, the name parsing interface identifying the type of the name and providing a name-type specific object to the client application program; and the name-type specific system object exposing a programming interface to the client application program wherein the programming interface includes a retrieval function, wherein the client application program initiates asynchronous retrieval of data for the named item through the retrieval function, and wherein the client application program continues instruction execution independently of the asynchronous retrieval of data.
Claim 74
Dependent Claim
159 words
An object-oriented framework for providing asynchronous retrieval of data for a named item for a client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program further includes a name that references the named item, the object-oriented framework comprising: a name parsing interface accessible to the client application program and operating to parse a name passed from the client application program in a request issued by the client application program to the interface, the name parsing interface identifying the type of the name and providing a name-type specific object to the client application program; and the name-type specific system object exposing a programming interface to the client application program wherein the programming interface includes a retrieval function, wherein the client application program initiates asynchronous retrieval of data for the named item through the retrieval function, and wherein the client application program continues instruction execution independently of the asynchronous retrieval of data.
Claim 75
Dependent Claim
19 words
The object-oriented framework of claim 64 wherein the name-type specific system object encapsulates name to named item association data.
Claim 76
Dependent Claim
16 words
The object-oriented framework of claim 64 wherein the name-type specific system object is a moniker object.
Claim 77
Dependent Claim
131 words
An object-oriented framework for providing asynchronous data retrieval for a named item for a client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program further includes a name that references the named item, the object-oriented framework comprising: a service object that instantiates one or more system objects, wherein the service object is callable from a client applicatino program; and a system object that exposes a programming interface to the client application program, wherein the service object instantiates the system object, wherein the programming interface includes a retrieval function, wherein the client application program initiates asynchronous retrieval of data for the named item through the retrieval function, and wherein the client application program continues instruction execution indenpendently of the asynchronous retrieval of data.
Claim 78
Dependent Claim
131 words
An object-oriented framework for providing asynchronous data retrieval for a named item for a client application program, wherein the client application program includes plural instructions for executing, and wherein the client application program further includes a name that references the named item, the object-oriented framework comprising: a service object that instantiates one or more system objects, wherein the service object is callable from a client applicatino program; and a system object that exposes a programming interface to the client application program, wherein the service object instantiates the system object, wherein the programming interface includes a retrieval function, wherein the client application program initiates asynchronous retrieval of data for the named item through the retrieval function, and wherein the client application program continues instruction execution indenpendently of the asynchronous retrieval of data.
Claim 79
Dependent Claim
16 words
The object-oriented framework of claim 67 wherein the service object instantiates a name-type specific system object.
Claim 80
Independent Claim
73 words
A method for encapsulating asynchronously retrieved data within an object for a client application program, wherein the client application program includes plural instructions for executing, the method comprising: de-referencing a data type to an object type; instantiating an object of the object type; asynchronously retrieving the data, wherein the client application program continues instruction execution independently of the asynchronous retrieval of the data; and encapsulating the asynchronously retrieved data within the instantiated object.
Claim 81
Independent Claim
73 words
A method for encapsulating asynchronously retrieved data within an object for a client application program, wherein the client application program includes plural instructions for executing, the method comprising: de-referencing a data type to an object type; instantiating an object of the object type; asynchronously retrieving the data, wherein the client application program continues instruction execution independently of the asynchronous retrieval of the data; and encapsulating the asynchronously retrieved data within the instantiated object.
References Cited (Backward Citations)
US4514800A
Cited
US4739477A
Cited
US4674040A
Cited
US4962475A
Cited
US4815029A
Cited
US5249275A
Cited
US5072412A
Cited
US5369778A
Cited
US5206951A
Cited
US4933880A
Cited
US5313646A
Cited
US5339423A
Cited
US5297283A
Cited
US5551035A
Cited
US5410688A
Cited
US5381547A
Cited
JPH03191429A
Cited
US5333317A
Cited
US5440744A
Cited
US5341478A
Cited
US5237680A
Cited
US5204947A
Cited
US5297249A
Cited
US5191645A
Cited
US5187786A
Cited
US5339424A
Cited
US5517655A
Cited
US5274803A
Cited
US5481722A
Cited
US5664178A
Cited
US5842018A
Cited
JP3191429B2
Cited
US5581686A
Cited
US5535389A
Cited
US5764984A
Cited
US5446842A
Cited
US5369766A
Cited
US5459865A
Cited
US5408665A
Cited
US5577252A
Cited
US5838906A
Cited
US5815830A
Cited
US5706501A
Cited
US5634121A
Cited
US5745683A
Cited
US6016520A
Cited
US5572643A
Cited
US5758358A
Cited
US5659729A
Cited
US5761683A
Cited
US5963964A
Cited
US5778372A
Cited
US6026416A
Cited
US5854630A
Cited
US6031989A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2005-06-03 | 2005-12-03 | 2006-06-04 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2009-06-03 | 2009-12-03 | 2010-06-04 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2013-06-03 | 2013-12-03 | 2014-06-04 | $7700.00 | Window Closed / Lapsed |