Browse Prior Art Database

Maintaining affinity of message groups

IP.com Disclosure Number: IPCOM000013106D
Original Publication Date: 2003-Jun-13
Included in the Prior Art Database: 2003-Jun-13
Document File: 1 page(s) / 38K

Publishing Venue

IBM

Abstract

This scheme enables a group of messages to flow through a network so that both the final destination and the route are fixed when the first message starts to flow. There is no requirement that the full membership of the group is known until the last messages starts to flow.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 1

Maintaining affinity of message groups

When sending data as a set of messages it is often necessary to send a group of messages to the same destination. The destination may be a queue, physical machine, or application. The scheme below is useful if there is a choice of several potential destinations or a choice of routes to reach a given destination, giving the possibility that messages may be reordered by following different routes to the destination. It is sometimes necessary to avoid storing all of the messages in a group in a single system before making the decision as to where to send them. This can be because the messages are large and cannot be easily stored until the complete set is available. This situation frequently occurs if the group represents the data in a database that is to be replicated, or if it represents a file that is to be transferred.

    The messages are signalled to the software as being part of an identifiable group, the application also has to signal that the group is complete. The implication is that transmission must start before the group is complete, yet the originating system and any intermediate systems must retain the routing choice until transmission of the group has been completed. In this scheme messages in a group are flagged with a "follow me" indicator, meaning that the message following the current one must take the same route. Each system along the route must retain at least the last message it has received, with the routing decision it mad...