Application messaging system with flexible message header structure
First Claim
1. A method for messaging between applications in a distributed application system, comprising the steps of:
- generating a message at a first application, together with a message header information and a body information;
creating a flexible message header, including placing portions of the message header information and the body information into a plurality of typed container modules;
sending some or all of the plurality of typed container modules to a second application; and
reconstructing the message at the second application using some or all of the typed container modules.
1 Assignment
0 Petitions
Accused Products
Abstract
The Flexible Message Header (FMH) is a typed modular message structure comprising one or more Typed Container Modules (TCM)—stateful message modules with a compact header (Typed Container Header, TCH), a user definable payload (Typed Container Body, TCB), and a set of payload-specific callback to handle the lifecycle of the module at the different state such as creation, preparation, manipulation, resizing, transferring, and deletion. A single message comprises a small header with various numbers of TCMs. The integrity of the entire message is not affected by dynamically modifying, adding or removing TCM from the message. Major message content change can be achieved by either adding a TCM or swapping the TCM with different TCM. Minor message content change can be achieved by either modifying or expanding the TCM directly within the message. New features can be supported by adding new TCM and new code to process the new TCM.
-
Citations
19 Claims
-
1. A method for messaging between applications in a distributed application system, comprising the steps of:
-
generating a message at a first application, together with a message header information and a body information;
creating a flexible message header, including placing portions of the message header information and the body information into a plurality of typed container modules;
sending some or all of the plurality of typed container modules to a second application; and
reconstructing the message at the second application using some or all of the typed container modules. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A system for messaging between distributed applications, comprising:
-
a first application that generates a message, together with a message header information and a body information;
a function for creating a flexible message header, including segmenting the message header information and the body information into a plurality of typed container modules;
a function for sending the typed container modules to a second application; and
a second application that selects some of the typed container modules and using them to reconstruct the message. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A computer readable medium including instructions stored therein which when executed by a computer causes the computer to perform the steps of:
-
generating a message at a first application, together with a message header information and a body information;
creating a flexible message header, including placing portions of the message header information and the body information into a plurality of typed container modules;
sending some or all of the plurality of typed container modules to a second application; and
reconstructing the message at the second application using some or all of the typed container modules.
-
Specification