Locating and executing objects in a distributed network
First Claim
Patent Images
1. A system implemented on a client device, comprising:
- at least one processing unit;
an object manager component implemented by the at least one processing unit and configured to access a distributed object based on a Uniform Resource Identifier (URI) associated with the distributed object, wherein the distributed object is agnostic to remote procedures; and
an object processing component implemented by the at least one processing unit and configured to interact remotely with the distributed object, the remote interaction taking place over a distributed network, and the distributed object being configured to;
perform a first function of the distributed object, andoffload at least a portion of its functionality to a second distributed object, the at least a portion including a second function of the distributed object, the object processing component being unaware of an existence of the second distributed object.
2 Assignments
0 Petitions
Accused Products
Abstract
The subject disclosure relates to interaction and execution of objects in a distributed network or in the cloud. Each object comprises a Uniform Resource Identifier (URI) path that names the object in the cloud through a distributed object directory. A client device can directly interface with a live instance of an object based on the URI path. The object can be agnostic to remote procedure call semantics. In some aspects, the object can be connected to an interacted with either remotely or locally. Further, single instances or multiple instances of the object can exist at substantially the same time.
12 Citations
20 Claims
-
1. A system implemented on a client device, comprising:
-
at least one processing unit; an object manager component implemented by the at least one processing unit and configured to access a distributed object based on a Uniform Resource Identifier (URI) associated with the distributed object, wherein the distributed object is agnostic to remote procedures; and an object processing component implemented by the at least one processing unit and configured to interact remotely with the distributed object, the remote interaction taking place over a distributed network, and the distributed object being configured to; perform a first function of the distributed object, and offload at least a portion of its functionality to a second distributed object, the at least a portion including a second function of the distributed object, the object processing component being unaware of an existence of the second distributed object. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method, comprising:
-
accessing, by a processing unit on a client device, a distributed object based on a request for a Uniform Resource Identifier (URI) received from a client device, the distributed object being enabled to be utilized irrespective of remote procedure semantics; and interacting remotely, by the processing unit on the client device, with the distributed object, the remote interaction taking place over a distributed network, the distributed object performing a first function of the distributed object and offloading at least a portion of its functionality, that includes a second function of the distributed object, to a second distributed object, the processing unit on the client device being unaware of an existence of the second distributed object. - View Dependent Claims (10, 11, 12, 13, 14, 15)
-
-
16. A system implemented on a client device, comprising:
-
at least one processing unit; an object manager component implemented by the at least one processing unit and configured to access a distributed object based on a Uniform Resource Identifier (URI) associated with the distributed object, wherein the distributed object is agnostic to remote procedures; and an object processing component implemented by the at least one processing unit and configured to execute a method of the distributed object remotely, the execution taking place over a distributed network, the distributed object being configured to; perform a first function of the distributed object, and offload at least a portion of its functionality to a second distributed object, the at least a portion including a second function of the distributed object, the object processing component being unaware of an existence of the second distributed object. - View Dependent Claims (17, 18, 19, 20)
-
Specification