Virtual machine communication

• US 8,505,029 B1
• Filed: 11/26/2007
• Issued: 08/06/2013
• Est. Priority Date: 11/26/2007
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Chanda, Rupen, Campbell, Chris
• Primary Examiner(s): Sough, H S
• Assistant Examiner(s): DORAIS, CRAIG C
• Application Number:
  US11/945,180
• Time in Patent Office: 2,080 Days
• Field of Search: None
• US Class Current: 719/313
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

The present disclosure includes, among other things, systems, methods and program products for virtual machine communication. For example, one or more aspects of the subject matter described in this disclosure can be embodied in one or more methods that include constructing a first message on behalf of a first program executing in a first virtual machine. A second virtual machine is selected from one or more virtual machines. Security information for the first program is communicated to the second virtual machine. The first message is communicated from the first virtual machine to the second virtual machine, the first message to be processed by the second virtual machine with regard to the security information.

Claims

1. A computer-implemented method, comprising:

constructing a first message on behalf of a first program executing in a first virtual machine;

selecting a second virtual machine from one or more virtual machines;

communicating security information for the first program to the second virtual machine, where the security information indicates a security sandbox associated with the first program;

communicating the first message from the first virtual machine to the second virtual machine, the first message to be processed by the second virtual machine with regard to the security information and the security sandbox,

where communicating the security information and communicating the first message are performed without remote method invocation (RMI), stub, and skeleton components.

2. The method of claim 1 where the security information includes a domain of the first program.

3. The method of claim 1, further comprising:

receiving the first message by the second virtual machine;

selecting a second program to process the first message; and

invoking the second program.

4. The method of claim 1, further comprising:

communicating a second message from the second virtual machine to the first virtual machine;

receiving the second message by the first virtual machine;

selecting a second program to process the second message; and

invoking the second program.

5. The method of claim 1 where selecting a second virtual machine is based on a status of the second virtual machine.

6. The method of claim 5 where the status indicates whether the second virtual machine is able to accept a message.

7. The method of claim 1 where the message includes a set of name and value pairs.

8. The method of claim 1 where the first program does not take part in communicating the security information and communicating the first message.

9. A computer program product, encoded on a non-transitory computer-readable medium, operable to cause data processing apparatus to perform operations comprising:

constructing a first message on behalf of a first program executing in a first virtual machine;

selecting a second virtual machine from one or more virtual machines;

communicating security information for the first program to the second virtual machine, where the security information indicates a security sandbox associated with the first program; and

communicating the first message from the first virtual machine to the second virtual machine, the first message to be processed by the second virtual machine with regard to the security information and the security sandbox,

where communicating the security information and communicating the first message are performed without remote method invocation (RMI), stub, and skeleton components.

10. The computer program product of claim 9 where the security information includes a domain of the first program.

11. The computer program product of claim 9 where the operations further comprise:

receiving the first message by the second virtual machine;

selecting a second program to process the first message; and

invoking the second program.

12. The computer program product of claim 9 where the operations further comprise:

communicating a second message from the second virtual machine to the first virtual machine;

receiving the second message by the first virtual machine;

selecting a second program to process the second message; and

invoking the second program.

13. The computer program product of claim 9 where selecting a second virtual machine is based on a status of the second virtual machine.

14. The computer program product of claim 13 where the status indicates whether the second virtual machine is able to accept a message.

15. The computer program product of claim 9 where the message includes a set of name and value pairs.

16. The computer program product of claim 9 where the first program does not take part in communicating the security information and communicating the first message.

17. A system comprising:

a first virtual machine on a first computing device;

a second virtual machine on a second computing device; and

where the first computing device has encoded on a computer-readable medium instructions operable to cause the first computing device to perform operations comprising;

constructing a first message on behalf of a first program executing in the first virtual machine;

communicating security information for the first program to the second virtual machine, where the security information indicates a security sandbox associated with the first program; and

communicating the first message from the first virtual machine to the second virtual machine, the first message to be processed by the second virtual machine with regard to the security information and the security sandbox,

where communicating the security information and communicating the first message are performed without remote method invocation (RMI), stub, and skeleton components.

18. The system of claim 17 where the first computing device is distinct from the second computing device.

19. The system of claim 17 where the security information includes a domain of the first program.

20. The system of claim 17, further comprising:

receiving the first message by the second virtual machine;

selecting a second program to process the first message; and

invoking the second program.

21. The system of claim 17, further comprising:

communicating a second message from the second virtual machine to the first virtual machine;

receiving the second message by the first virtual machine;

selecting a second program to process the second message; and

invoking the second program.

22. The system of claim 17 where selecting a second virtual machine is based on a status of the second virtual machine.

23. The system of claim 22 where the status indicates whether the second virtual machine is able to accept a message.

24. The system of claim 17 where the message includes a set of name and value pairs.

25. The system of claim 17 where the first program does not take part in communicating the security information and communicating the first message.