Process for operating a distributed computer network comprising several distributed computers

• US 20020174169A1
• Filed: 07/16/2001
• Published: 11/21/2002
• Est. Priority Date: 05/21/2001
• Status: Abandoned Application

• Current Assignee: Hans Albrecht Schmid
• Original Assignee: Hans Albrecht Schmid
• Inventors: Schmid, Hans Albrecht
• Application Number:
  US09/905,184
• Publication Number:
  US 20020174169A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The invention relates to a process for operating a distributed computer network. The computer network has several distributed computers, on one of the computers there being a component of a computer program, a component which can run on the microprocessor of the computer. To operate the computer the component is accessed from a collocated client or a remote client. To accelerate processing of the computer program, it is proposed that the component be accessed from the collocated client via the local gate of the component if the component is filed on the same computer and runs within the same execution environment as the client, and otherwise the component is accessed from the remote client optionally via a proxy via a remote gate of the component.

Claims

1. A process for operating a distributed computer network comprising a plurality of distributed computers, on one of the computers there being at least one component of a computer program, a component which can run on the microprocessor of the computer, and to operate the computer the at least one component being accessed from a collocated client, or a remote client, the at least one component is accessed from the collocated client via a local gate of the at least one component if the collocated client is filed on the same computer and runs within a same execution environment as the at least one component, and otherwise the at least one component is accessed from the remote client via a remote gate of the at least one component.

3. The process as claimed in claim 1, wherein from the at least one component, at least one other component is accessed via a local gate of the at least one other component, if the at least one other component is filed on the same computer and runs within the same execution environment as the at least one component and otherwise from the at least one component, the at least one other component is accessed via a remote gate, of the at least one other component.

4. The process as claimed in claim 1, wherein the remote gate of the at least one component is accessed via a proxy, the proxy implementing a same interface as the local gate.

5. The process as claimed in claim 3, wherein the remote gate of the at least one component, is used for transformation of a parameter or a result when services or functionalities of the at least one component have parameters or results which themselves represent a reference to the at least one other component and the at least one other component is located locally with respect to the at least one component, but remotely with respect to the client.

6. The process as claimed in claim 4, wherein the proxy is used for transformation of a parameter or a result when services or functionalities of the at least one component have parameters or results which themselves represent a reference to another proxy and the at least one other component, is located remotely with reference to the at least one component, but collocated with reference to the client.

7. The process as claimed in claim 1, wherein to access the at least one component, first a local naming and directory service is accessed and from it a reference to the at least one component to be invoked is transferred, the reference referring to a local gate of the at least one component if the at least one component to be invoked is a collocated component, and the reference refers via a proxy to a remote gate of the at least one component if the at least one component to be invoked is a remote component.

8. The process as claimed in claim 7, wherein to access the at least one component, first the local naming and directory service is accessed and from it a reference to a factory (19) of the at least one component to be invoked is transferred, the reference referring to the local gate of the factory if the factory and the at least one component to be invoked are collocated, and the reference is packed into a proxy refers to the remote gate of the factory when the factory and the at least one component to be invoked are remote, and another reference to the at least one component to be invoked is transferred by the factory, the at least one other reference referring to a local gate of the at least one component, if the factory and the at least one component to be invoked are collocated, and the other reference is packed into a proxy, refers to a remote gate, of the at least one component if the factory and the at least one component to be invoked are remote.

2. A process for operating the computer of a distributed computer network comprising the computer and a plurality of distributed computers, on the computer there being at least one component of a computer program, a component which can run on the microprocessor of the computer, and to operate the computer the at least one component is accessed from a collocated client or a remote client, wherein the at least one component is accessed from the collocated client, via a local gate of the at least one component, if the at least one component is filed on the same computer and runs within a same execution environment as the collocated client, and otherwise the at least one component is accessed from the remote client, via a remote gate of the at least one component.

9. A computer program which can run on a microprocessors of a plurality of computers of a distributed computer network, comprising at least one component, with at least one gate for accessing the at least one component, from a collocated client, which is filed on a same computer, and runs within a same execution environment as the at least one component, or from a remote client, which is filed on another computer and runs within an execution environment other than the at least one component, wherein the at least one component has a local gate for access to the at least one component from the collocated client and a remote gate for access to the at least one component from the remote client.

10. A storage element, selected from a read-only memory, a random access memory, or a flash memory for a computer of a distributed computer network on which at least one component of a computer program which can run on the microprocessors of the computer of the computer network is stored, the at least one component having at least one gate for accessing the at least one component from a collocated client which is filed on a same computer and runs within the same execution environment as the at least one component, or from a remote client which is filed on another computer and runs within an execution environment other than the at least one component, wherein the at least one component has a local gate for access to the at least one component from the collocated client and a remote gate for access to the at least one component from the remote client.

11. A computer of a distributed computer network with a storage element, selected from a read-only memory, a random access memory, or a flash memory on which at least one component of a computer program which can run on the microprocessors of the computers of the computer network is stored, the at least one component having at least one gate for accessing the at least one component from a collocated client which is filed on the same computer and runs within a same execution environment as the at least one component, or from a remote client which is filed on another computer and runs within an execution environment other than the at least one component, wherein the at least one component has a local gate for access to the at least one component from the collocated client and a remote gate for access to the at least one component from the remote client.

12. A distributed computer network comprising several computers with one storage element each, selected from a read-only memory, a random access memory, or a flash memory on which at least one component of a computer program which can run on the microprocessors of the computers of the computer network is stored, the at least one component having at least one gate for accessing the at least one component from a collocated client which is filed on the same computer and runs within the same execution environment as the at least one component, or from a remote client which is filed on another computer and runs within an execution environment other than the at least one component, wherein the at least one component has a local gate for access to the at least one component from the collocated client and a remote gate for access to the at least one component from the remote client.