Method and system for communicating between application software

A method facilitating communication between at least two hosts, each of said hosts comprising an application software component that is divided into software entities, said method comprising the steps of:

• creating messages by a software entity on a first host of said at least two hosts destined for any of remaining of said at least two hosts and writing said messages into an output queue;
• fetching said messages by a messaging software component on said first host;
• deciding type of communication by said messaging software component;
• if said communication is intra-host, writing said messages into an input queue of another software entity residing on said first host, and
• if said communication is inter-host, writing said messages into a connection output queue for said any of the remaining of at least two hosts that the messages are destined for in said first host, sending said messages by said messaging software component on said first host to a messaging software component on said any of the remaining of at least two hosts, receiving said messages by said messaging software component in said any of the remaining of at least two hosts and writing said messages into a connection input queue by said messaging software component and further writing said messages to an input queue of a software entity residing on said any of the remaining of at least two hosts, and
• said messages used in any of the following mechanisms:
• registration and deregistration mechanism, cold startup mechanism or a life cycle mechanism,
• said registration/deregistration mechanism used by each of said software entities on said at least two hosts to register/deregister themselves to/from said system, said registration/deregistration mechanism performing step of:
• registering said software entities residing on a first host with said messaging software component on said first host at startup;
• establishing for each of said registered software entities on said first host, input and output message queues in an inter-process shared memory, together with creating traffic dispatcher threads;
• distributing registration information on said first host to said remaining of said at least two hosts periodically by using a (Transmission Control Protocol/Internet Protocol) TCP/IP connection, and releasing said input and output queues in said inter-process shared memory when any of said registered software entities is no longer functional;
• said cold startup mechanism further comprising:
• obtaining a list of software entities from remaining of said at least two hosts using a RIP protocol;
• constructing a list of software entities known to said first host including software entities registered locally to said first host and said list of software entities obtained from step above, and sending said constructed list to said remaining of said at least two hosts using said (routing information protocol) RIP protocol;
• and
• said lifecycle management mechanism used by messaging software component on said first host to monitor state software entities residing on said first host, said mechanism performing the steps of:
• associating a state with each of said software entities via a state machine;
• receiving state change messages from each of said software entities relating to traffic processing capabilities by said messaging software component on said first host, and updating a RIP routing table stored in said messaging software component on said first host and sending said table to each of said remaining at least two hosts via said messaging software component.