Message send version management in network

• US 8,656,054 B2
• Filed: 04/30/2008
• Issued: 02/18/2014
• Est. Priority Date: 04/30/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Anna, Gary, Dain, Joseph Whitney
• Primary Examiner(s): Wang, Liangche A
• Assistant Examiner(s): JOSHI, SURAJ M
• Application Number:
  US12/112,737
• Publication Number:
  US 20090276480A1
• Time in Patent Office: 2,120 Days
• Field of Search: None
• US Class Current: 709/246
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 specially adapted for interworking of IP-based networks with other networks

Abstract

An apparatus, method, and computer program product for message send version management in a distributed computing environment including a plurality of nodes is provided. A message is sent from a first node of the plurality of nodes to at least one additional node of the plurality of nodes. At least one translation vector is constructed to translate between multiple message versions is constructed. The at least one translation vector is send from the first node to the at least one additional node. In one embodiment, the at least one translation vector is attached to the message to generate a packet.

Claims

1. A method for message version management in a distributed computing environment including a plurality of nodes, a message sent from a first node of the plurality of nodes to at least one additional node of the plurality of nodes, comprising:

determining a first application version of the message supported by the at least one additional node;

utilizing the at least one translation vector to translate between a second message version of the message supported by the first node and the first version based on the determination;

sending, from the first node to the at least one additional node, the message accompanied by at least one translation vector in an initial occurrence of the message;

storing, by the at least one additional node, the at least one translation vector; and

utilizing the stored at least one translation vector in at least one subsequent occurrence of the message,

wherein the second version is a newer version than the first version and utilizing the at least one translation vector comprises constructing the first version of the message by obtaining portions of the message from the second version of the message utilizing a byte offset and providing a position to the portions in the first version of the message utilizing a new byte offset such that at least one portion of the message comprises a different offset in the first version and second version of the message.

2. The method of claim 1, wherein sending the at least one translation vector from the first node to the at least one additional node includes attaching the at least one translation vector to the message to generate a packet.

3. The method of claim 1, wherein constructing a translation vector to translate between multiple message versions includes:

examining a translation table, and

modifying the message according to the translation table to be compatible across multiple message versions.

4. The method of claim 3, wherein modifying the message according to the translation table includes truncating, adding, deleting, moving, or concatenating at least a portion of the message.

5. The method of claim 1, further including:

examining a translation table to be compatible across multiple message versions, and

examining a field to designate at least one target node.

6. The method of claim 2, further including sending the packet, including the message and the at least one translation vector, to the at least one additional node.

7. The method of claim 1, further including attaching a header to at least one of the message or the translation vector to identify the message or the translation vector.

8. The method of claim 1, further including, subsequent to sending the translation vector, updating a field in the table to reflect sending the at least one translation vector.

9. The method of claim 1, wherein utilizing the stored at least one translation vector comprises utilizing the stored at least one translation vector in each subsequent occurrence of the message.

10. An administrator device for message version management in a distributed computing environment including a plurality of nodes, a message sent from a first node of the plurality of nodes to at least one additional node of the plurality of nodes, comprising:

a processor; and

memory coupled to the processor, the memory comprising;

a message module operable on a sending application in communication with the plurality of nodes, wherein the message module is adapted for;

determining a first application version of the message supported by the at least one additional node,

utilizing at least one translation vector to translate between a second message version of the message supported by the first node and the first version based on the determination,

sending, from the first node to the at least one additional node, the message accompanied by at least one translation vector in an initial occurrence of the message,

storing, by the at least one additional node, the at least one translation vector, and

further utilizing the at least one translation vector in at least one additional occurrence of the message,

wherein the second version is a newer version than the first version and utilizing the at least one translation vector comprises constructing the first version of the message by obtaining portions of the message from the second version of the message utilizing a byte offset and providing a position to the portions in the first version of the message utilizing a new byte offset such that at least one portion of the message comprises a different offset in the first version and second version of the message.

11. The device of claim 10, wherein the message module is further adapted for attaching the at least one translation vector to the message to generate a packet.

12. The device of claim 10, wherein the message module is further adapted for:

examining a translation table, and

modifying the message according to the translation table to be compatible across multiple message versions.

13. The device of claim 12, wherein the message module is further adapted for truncating, adding, deleting, moving, or concatenating at least a portion of the message to modify the message.

14. The device of claim 11, wherein the message module is further adapted for sending the packet, including the message and the at least one translation vector, to the at least one additional node.

15. The device of claim 10, wherein the at least one translation vector is adapted for either of:

(a) translation from a higher message version to a lower message version, and

(b) translation from a lower message version to a higher message version.

16. The device of claim 10, wherein, when utilizing the stored at least one translation vector, the message module is further adapted for utilizing the stored at least one translation vector in each subsequent occurrence of the message.

17. A computer program product for message version management in a distributed computing environment including a plurality of nodes, a message sent from a first node of the plurality of nodes to at least one additional node of the plurality of nodes, the computer program product comprising a computer-readable storage device having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for determining a first application version of the message supported by the at least one additional node;

a second executable portion for utilizing at least one translation vector to translate between a second message version of the message supported by the first node and the first version based on the determination;

a third executable portion for sending, from the first node to the at least one additional node, the message accompanied by at least one translation vector in an initial occurrence of the message;

a fourth executable portion for storing, by the at least one additional node, the at least one translation vector; and

a fifth executable portion for utilizing the stored at least one translation vector in at least one subsequent occurrence of the message,

wherein the second version is a newer version than the first version and utilizing the at least one translation vector comprises constructing the first version of the message by obtaining portions of the message from the second version of the message utilizing a byte offset and providing a position to the portions in the first version of the message utilizing a new byte offset such that at least one portion of the message comprises a different offset in the first version and second version of the message.

18. The computer program product of claim 17, wherein the second executable portion includes a sixth executable portion for:

examining a translation table, and

modifying the message according to the translation table to be compatible across multiple message versions.

19. The computer program product of claim 17, further including a seventh executable portion for sending the packet, including the message and the at least one translation vector, to the at least one additional node.

20. The computer program product of claim 17, wherein the third executable portion includes a sixth executable portion for utilizing the stored at least one translation vector in each subsequent occurrence of the message.