Coordination of set enumeration information between independent agents

• US 7,774,405 B2
• Filed: 05/16/2005
• Issued: 08/10/2010
• Est. Priority Date: 05/16/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bernabeu-Auban, Jose M., Peschel-Gallee, Frank V.
• Primary Examiner(s): Srivastava; Vivek
• Assistant Examiner(s): Jakovac; Ryan J
• Application Number:
  US11/130,300
• Publication Number:
  US 20060259541A1
• Time in Patent Office: 1,912 Days
• Field of Search: 709/202
• US Class Current: 709/202
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548

Abstract

A type server on a first machine assigns a sequential small integer identifier of fixed length to lengthy information. Identifying information using a small integer identifier provides efficiencies in communication between processes on a single machine as well as efficiencies in communication between processes on different machines. Storage of this information is also more efficient. The information so identified may be, for example, interface type. The small integer identifier assigned to the interface types may be assigned in a set enumeration scheme, that is the first interface type encountered when generating a list or table of interfaces types may be assigned the integer identifier “1”, the second “2” and so on. Similarly, the small integer identifiers may be assigned whenever a new interface type is encountered during execution. A translation table including interface type name and interface type identifier for may be generated.

Claims

1. A system for correlating identifiers on different computers comprising:

a first agent on a first computer that is adapted to receive a message from a second agent on the first computer, wherein the second agent is adapted to send the message to a second computer, the message comprising;

a first identifier for a resource, wherein the first identifier is a first integer assigned to the resource as the resource is encountered in a process running on the first computer, wherein the resource is identified by a second identifier on the second computer, the second identifier comprising a second integer not equal to the first integer, wherein the first agent on the first machine is adapted to replace the first identifier with the second identifier in the message to be sent to the second computer; and

a table of entries comprising at least one table entry for correlating between

the first integer and the second integer, wherein the first agent is adapted to send a request to the second computer for the second identifier when the second identifier is not found in the table of entries.

2. The system of claim 1, wherein the table entry comprises a resource name.

3. The system of claim 1, wherein the table entry comprises the first identifier assigned to the resource on the first computer.

4. The system of claim 1, wherein the table entry comprises the second identifier assigned to the resource on the second computer.

5. The system of claim 1, further comprising a type server, the type server assigning the first identifier to the resource as the resource is encountered in execution.

6. A computer-implemented method for correlating between a first identifier assigned to a resource on a first computer and a second identifier assigned to the resource on a second computer comprising:

generating a table comprising the first identifier and the second identifier, wherein the first identifier comprises an identifier for the resource for the first computer and the second identifier comprises an identifier for the resource for the second computer;

replacing, using a first agent on the first computer, the first identifier with the

second identifier in a message before sending the message to the second computer; and

requesting, using the first agent on the first computer, the second identifier

assigned to the resource on the second computer if the second identifier is not found in the table.

7. The method of claim 6, further comprising:

receiving a message from the first agent on the first computer to be sent to a second agent on the second computer, the message comprising the first identifier.

8. The method of claim 6, further comprising:

receiving the second identifier from the second computer.

9. The method of claim 8, further comprising:

storing the first identifier and the second identifier in the table correlating identifiers on the first computer.

10. The method of claim 9, further comprising:

storing the first identifier and the second identifier in a table correlating identifiers on the second computer.

11. A physical computer-readable storage medium comprising computer-executable instructions for:

generating a table correlating a first identifier assigned to an interface type on a first computer and a second identifier assigned to the interface type on a second computer;

receiving a message from a first agent on the first computer to be sent to a second agent on the second computer, the message comprising the first identifier and a interface type name; and

replacing at the first computer the first identifier with the second identifier from the correlation table assigned to the interface type on the second computer.

in response to determining that the second identifier assigned to the interface

type on the second computer is missing from the correlation table, sending a message to the second computer requesting the second identifier;

receiving the second identifier from the second computer and storing the second identifier in the correlation table;

generating a second correlation table on the second computer; and

receiving the message from the first computer, the message comprising the first identifier and storing the first identifier in the second correlation table.

12. The computer-readable medium of claim 11, comprising further instructions for:

assigning a four-byte integer as the first identifier.