MESSAGE RECEIPT VERSION MANAGEMENT IN NETWORK

• US 20090276481A1
• Filed: 04/30/2008
• Published: 11/05/2009
• Est. Priority Date: 04/30/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: DAIN, Joseph Whitney, ANNA, Gary
• Granted Patent: US 7,873,745 B2
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A method, apparatus, and computer program product for message receipt version management in a distributed computing environment including a plurality of nodes is provided. At least one translation vector is received in at least one additional node of the plurality of nodes from a first node. The translation vector provides information for the at least one additional node to translate between multiple message versions. A message is translated between versions according to the at least one translation vector. The translated message is forwarded to an application program. In one embodiment, the at least one translation vector is stored for future use.

Claims

1. A method for message version management in a distributed computing environment including a plurality of nodes, comprising:

receiving at least one translation vector in at least one additional node of the plurality of nodes from a first node, the at least one translation vector providing information for the at least one additional node to translate between multiple message versions;

translating a message between versions according to the at least one translation vector to generate a translated message; and

forwarding the translated message to an application program.

2. The method of claim 1, further including storing the at least one translation vector on the at least one additional node for future use.

3. The method of claim 2, wherein receiving the at least one translation vector includes receiving a packet including the at least one translation vector attached to a message.

4. The method of claim 2, further including, subsequent to storing the at least one translation vector on the at least one additional node, updating a field to reflect a receipt of the at least one translation vector.

5. The method of claim 3, wherein updating a field includes updating a first time receipt field to reflect a first time receipt of the at least one translation vector.

6. The method of claim 1, further including requesting a compatible translation vector from one of the plurality of nodes.

7. The method of claim 2, further including subsequent to storing the at least one translation vector on the at least one additional node:

receiving an additional message from the first node,

retrieving the at least one translation vector, and

translating the additional message according to the at least one translation vector.

8. The method of claim 1, wherein translating the message between versions according to the at least one translation vector includes modifying the message.

9. The method of claim 8, wherein modifying the message includes one of truncating, deleting, adding, moving, and concatenating the message.

13. The device of claim 9, wherein the message module is further adapted for requesting a compatible translation vector from the first node.

10. An administrator device for message version management in a distributed computing environment including a plurality of nodes, comprising:

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

receiving at least one translation vector in at least one additional node of the plurality of nodes from a first node, the at least one translation vector providing information for the at least one additional node to translate between multiple message versions,

translating a message between versions according to the at least one translation vector to generate a translated message, and

forwarding the translated message to an application program.

11. The device of claim 10, wherein the message module is further adapted for storing the at least one translation vector on the at least one additional node for future use.

12. The device of claim 11, wherein the message module is further adapted for, subsequent to storing the at least one translation vector, updating a field to reflect a receipt of the at least one translation vector.

14. The device of claim 11, wherein the message module is further adapted for, subsequent to storing the at least one translation vector:

receiving an additional message from the first node,

retrieving the at least one translation vector, and

translating the additional message according to the at least one translation vector.

15. The device of claim 10, wherein the message module is further adapted for modifying the message to translate the message between versions according to the translation vector.

16. The device of claim 15, wherein the message module is further adapted for one of truncating, deleting, adding, moving, and concatenating the message to modify the message.

18. The computer program product of claim 16, further including a fourth executable portion for storing the at least one translation vector on the at least one additional node for future use.

17. A computer program product for message version management in a distributed computing environment including a plurality of nodes, the computer program product comprising a computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for receiving an at least one translation vector in at least one additional node of the plurality of nodes from a first node, the at least one translation vector providing information for the at least one additional node to translate between multiple message versions;

a second executable portion for translating a message between versions according to the at least one translation vector to generate a translated message; and

a third executable portion for forwarding the translated message to an application program.

19. The computer program product of claim 17, wherein the fourth executable portion for storing the at least one translation vector on the at least one additional node includes a fifth executable portion for storing the at least one translation vector on a storage area including one of a message table, array, database, volatile memory, nonvolatile memory, and link list.

20. The computer program product of claim 17, further including a fifth executable portion for, subsequent to storing the at least one translation vector on the at least one additional node:

receiving an additional message from the first node,

retrieving the at least one translation vector, and

translating the additional message according to the at least one translation vector.