AU2014200243B2

AU2014200243B2 - System(s) and method(s) for multiple sender support in low latency fifo messaging using tcp/ip protocol

Info

Publication number: AU2014200243B2
Application number: AU2014200243A
Authority: AU
Inventors: Nishant Kumar Agrawal; Manoj Karunakaran Nambiar; Payal Guha Nandy
Original assignee: Tata Consultancy Services Ltd
Current assignee: Tata Consultancy Services Ltd
Priority date: 2013-11-08
Filing date: 2014-01-15
Publication date: 2015-06-18
Anticipated expiration: 2034-01-15
Also published as: CN104639597B; AU2014200243A1; CN104639597A; IN2013MU03528A

Abstract

SYSTEM(S) AND METHOD(S) FOR MULTIPLE SENDER SUPPORT IN LOW LATENCY FIFO MESSAGING USING TCP/IP PROTOCOL Systems and methods for transmitting and receiving multiple messages for multiple senders in low latencies, high throughput using TCP/IP Protocol is described. System comprises Network Interface Card enabled for TCP/IP, message library allowing messaging simultaneously in lockless manner. Transmitting system maps each remote sender process to each First in First Out (FIFO) sub-queue with host node and maps each remote sender process with corresponding remote receiver process with receiving node, arranges messages received from user in FIFO sub-queue dedicated for each user, transmits messages from each FIFO sub-queue to remote receiver process using remote sender process. Receiving system maps each remote receiver process to each FIFO sub-queue with receiving node and maps each remote receiver process with remote sender process with sending node, receives messages transmitted from user via remote receiver processes, arranges messages in FIFO sub-queue dedicated for each user, reads messages from each FIFO sub-queue using round-robin technique. SY:1 (102) SYSTEM SMQ) ELECTRONIC DEVICES(1004 ----------------

Description

P/00/011 Regulation 3.2 AUSTRALIA Patents Act 1990 ORIGINAL COMPLETE SPECIFICATION STANDARD PATENT Invention Title: "SYSTEM(S) AND METHOD(S) FOR MULTIPLE SENDER SUPPORT IN LOW LATENCY FIFO MESSAGING USING TCP/IP PROTOCOL" The following statement is a full description of this invention, including the best method of performing it known to me/us: SYSTEM(S) AND METHOD(S) FOR MULTIPLE SENDER SUPPORT IN LOW LATENCY FIFO MESSAGING USING TCP/IP PROTOCOL TECHNICAL FIELD [001] The present subject matter described herein, in general, relates to messaging systems, and more particularly to a system for supporting multiple senders in a low latency messaging using TCP/IP protocol. BACKGROUND [002] The important aspects of a messaging system are the latency and the throughput of messages. With the steady increase in network speeds, messaging systems are now expected to transfer millions of messages in few micro seconds between multiple publishers and subscribers. Various messaging systems used till today are with locking mechanism and suffers from the slow processing speed. In addition to this, they merely support messaging from single sender to single receiver. [003] One of the prior art process discloses a message bus in a messaging application for use in a data center provides a communication mechanism to provide low latency messaging. However, this application provides mechanism to send messages from a single sender to a single receiver. [004] Prior art processes failed to provide low latency messaging in seamless manner. The prior art method where messages are stored in queue where multiple writers are writing to the queue and when one of the writer is writing to the queue, others are locked for writing. Once first writer finishes his writing, there after another writer can write to the queue. The locking mechanism and multiple writing hamper the speed and performance of the messaging system. Therefore there is no requisite performance and speed of messaging attained by the system. 1 SUMMARY [005] This summary is provided to introduce aspects related to systems and methods for transmitting and receiving multiple messages hosted on at least one host node, in an inter-process communication and the aspects are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter. [006] In one implementation, a system for transmitting multiple messages hosted on at least one host node, in an inter-process communication is described. The system comprises a processor, a Network Interface Card (NIC) is coupled to the processor, wherein the NIC is enabled for Transmission Control Protocol / Internet Protocol (TCP/IP) to send the messages and a message library comprising one or more message-send and message receive functions allowing multiple messaging simultaneously in a lockless manner and a memory coupled to the processor. The processor is capable of executing a plurality of modules stored in the memory. The plurality of modules comprises a mapping module, an organizing module and a transmitting module. The mapping module is configured to map each of a remote sender process to each of a First in First out (FIFO) sub-queue associated with the host node and mapping each remote sender process with corresponding remote receiving process associated with a receiving node by using one or more memory mapped files. The organizing module is configured to arrange messages received from at least one user in the one or more FIFO sub-queue associated with the host node; wherein the FIFO sub-queue is dedicated for each user and is stored in a memory mapped file. The transmitting module is configured to transmit the messages from each FIFO sub-queue associated with the host node to the corresponding each remote receiving process associated with the receiving node using the corresponding remote sender process. [007] In another implementation, a system for receiving multiple messages hosted on at least one host node, in an inter-process communication is described. The system comprises a processor, a network interface card (NIC) coupled to the processor, wherein the NIC is enabled for TCP/IP to receive messages. The system further 2 comprises a messaging library comprising one or more message-send and message receive functions allowing multiple messaging simultaneously in a lockless manner and a memory coupled to the processor. The processor is capable of executing plurality of modules stored in the memory. The plurality of modules comprises a mapping module, a retrieving module and a reading module. The mapping module is configured to map each of a remote receiving process to each of a FIFO sub-queue associated with the receiving node and mapping each remote receiving process with corresponding remote sender process associated with a sending node by using one or more memory mapped files. The retrieving module is configured to receive the multiple messages transmitted from one or more host nodes with at least one user via a remote receiving processes dedicated for each user, the messages so received are arranged in a FIFO sub-queue, wherein each FIFO sub-queue is dedicated for each user and is stored in a memory mapping file. The reading module is configured to read the multiple messages from each of the FIFO sub-queue by using a round-robin technique in a FIFO mode. [008] In one implementation, a method for transmitting multiple messages hosted on at least one host node, in an inter-process communication is described. The method comprises executing message-send and message-receive functions allowing multiple messaging simultaneously in a lockless manner. The method further comprises transmitting multiple user messages using TCP/IP Protocol. The transmitting further comprises mapping each of a remote sender process to each FIFO sub-queue associated with the host node and mapping each remote sender process with corresponding remote receiving process associated with a receiving node by using one or more memory mapped files. The transmitting further comprises arranging messages received from at least one user in the one or more FIFO sub-queue associated with the host node; wherein the FIFO sub-queue is dedicated for each user and is stored in a memory mapped file. The transmitting further comprises transmitting the messages from each FIFO sub-queue associated with the host node to the corresponding each remote receiving process associated with the receiving node using the corresponding remote sender process. The mapping, the arranging and the transmitting is performed by means of the processor. 3 [009] In another implementation, a method for receiving multiple messages hosted on at least one host node, in an inter-process communication is described. The method comprises executing message-send and message-receive functions allowing multiple messaging simultaneously in a lockless manner and receiving multiple user messages using TCP/IP Protocol. The receiving of messages further comprises mapping each of a remote receiving process to each of a FIFO sub-queue associated with the receiving node and mapping each remote receiving process with corresponding remote sender process associated with a sending node by using one or more memory mapped files. The receiving of messages further comprises receiving the multiple messages transmitted from one or more host nodes with at least one user via a remote receiving processes dedicated for each user, the messages so received are arranged in a FIFO sub-queue, wherein each FIFO sub-queue is dedicated for each user and is stored in a memory mapped file. The receiving of messages further comprises reading the multiple messages from each of the FIFO sub-queue by using a round robin technique in a FIFO mode. The mapping, the receiving, the arranging and the reading is performed by means of the processor. BRIEF DESCRIPTION OF THE DRAWINGS [0010] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components. [0011] Figure 1 illustrates a network implementation of a system(s) for transmitting and receiving multiple messages hosted on at least one host node, in an inter-process communication shown, in accordance with an embodiment of the present subject matter. [0012] Figure 2 illustrates the system for transmitting multiple messages hosted on at least one host node, in accordance with an embodiment of the present subject matter. 4 [0013] Figure 3 illustrates the system for receiving multiple messages hosted on at least one host node, in accordance with an embodiment of the present subject matter. [0014] Figure 4 illustrates a configuration 1 for implementation of the present disclosure for transmitting and receiving the multiple messages hosted on at least one host node, in accordance with an exemplary embodiment of the present subject matter. [0015] Figure 5 illustrates a configuration 2 for implementation of the present disclosure for transmitting and receiving of the multiple messages hosted on at least one host node, in accordance with an exemplary embodiment of the present subject matter. [0016] Figure 6 illustrates a structure of the queue and sub-queue used in the present subject matter. [0017] Figure 7 illustrates a method for transmitting multiple messages hosted on at least one host node, in accordance with an embodiment of the present subject matter. [0018] Figure 8 illustrates a method for receiving multiple messages hosted on at least one host node, in accordance with an embodiment of the present subject matter. [0019] Figure 9 illustrates test setup for multiple publisher throughput tests, in accordance with an exemplary embodiment of the present subject matter. [0020] Figure 10 illustrates maximum throughput statistics for multiple publisher throughput test results, in accordance with an exemplary embodiment of the present subject matter. [0021] Figure 11 illustrates test setup for multiple publisher latency tests, in accordance with an exemplary embodiment of the present subject matter. [0022] Figure 12 illustrates test results for average round trip latency statistics for multiple publishers, in accordance with an exemplary embodiment of the present subject matter. 5 [0023] Figure 13 illustrates average round trip latency statistics at different throughput rates for multi publisher using TCP/IP over Ethernet, in accordance with an exemplary embodiment of the present subject matter. DETAILED DESCRIPTION [0024] Systems and methods for transmitting and receiving multiple messages hosted on at least one host node, in an inter-process communication are disclosed. The systems and methods of the present disclosure provide support for multiple publishers to write simultaneously to an asynchronous lockless message queue whose remote subscriber is connected to the publishers and messages are transferred using Transmission Control Protocol/Internet Protocol (TCP/IP). This disclosure facilitates multiple publishing streams to write to the messaging system while maintaining the inherent lockless capability. By this disclosure, multiple publishers may be enabled to write to the messaging framework simultaneously and the subscriber may be enabled to retrieve all the messages from all the publishers. The disclosure is implemented for local publishers and subscriber on the same physical system as well as remote publishers and subscriber on different physical messaging systems. The disclosure implements the support for multiple simultaneous publishers to an asynchronous lockless message queue. [0025] The present system and method implements the lockless messaging with multiple publishers wherein each publisher is assigned a dedicated sub-queue by the messaging system internally in a seamless manner (w/o manual intervention) giving the impression to all the publishers that they are writing to the same message queue simultaneously. The subscriber to a queue with multiple publishers reads from all the sub-queues in a round-robin fashion to get the messages in near FIFO fashion. With this implementation, all publishers write to their own sub-queues thus avoiding the need for locks and the subscriber receives the messages in the order in which each publisher inserts into their own sub-queues. The seamless assigning of sub-queues on arrival (using the system) of publishers and book keeping procedures on departure (not using the system) of publishers ensures sanctity of the messaging system. Referring to remote messaging systems, multiple dedicated remote sender and remote receiver 6 processes were spawned to ensure accurate sharing of the sub-queues on the remote systems. [0026] In accordance with an embodiment, the system and method for remote messaging in an inter-processes communication between at least two processes running on at least two remote nodes using transmission control protocol or internet protocol are disclosed in an Indian Patent Application 1546/MUM/2010 assigned to the applicant. The application specifically discloses remote messaging facilitation for single publisher and single subscriber on remote nodes using TCP/IP. The application 1546/MUIM/2010 discloses the system for messaging in inter-processes communication running on two nodes having a queue in a shared memory accessible by plurality of processes and writing process running on remote sender node, inserting message into the queue and remote sender process running on the remote sender node, asynchronously sending message from the queue. The remote receiving process running on a remote receiving node, synchronously receiving and inserting message into the queue stored on a shared memory of the remote receiving node and reading process, dequeueing the message from the queue stored on a shared memory of the remote receiving node. A free pointing element associated with a process adapted to point to a free storage buffer in the queue; and one data pointing elements associated with a process adapted to point to storage buffer containing an inter process message. The processes running at remote nodes transmit and receive the messages via a communication link adapted to facilitate connections between the processes from the group consisting of TCP/IP connection, GPRS connection, WiFi connection, WiMax connection and EDGE connection. The entire contents of the application 1546/MUM/2010 are incorporated as reference herein and are not repeated for the sake of brevity. [0027] While aspects of described systems and methods for transmitting and receiving multiple messages hosted on at least one host node may be implemented in any number of different computing systems, environments, and/or configurations, the embodiments are described in the context of the following exemplary system. 7 [0028] Referring now to Figure 1, a network implementation 100 of system 102 for transmitting multiple messages hosted on at least one host node is illustrated, in accordance with an embodiment of the present subject matter. In one embodiment, the system 102 receives multiple messages from a plurality of users in an inter process communication and arranges the messages so received. Further, the system 102 transmits the messages to the receiver. Further, a network implementation 100 of system 103 for receiving multiple messages hosted on at least one host node is illustrated, in accordance with an embodiment of the present subject matter. In one embodiment, the system 103 receives the multiple messages transmitted from one or more host nodes with at least one user. In another embodiment, the system 103 reads the multiple messages so received from one or more host nodes. [0029] Although the present subject matter is explained considering that the system 102 and the system 103 is implemented on one or more servers acting as a host node, it may be understood that the system 102 and the system 103 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, and the like. It will be understood that the system 102 and the system 103 may be accessed by multiple users through one or more user devices 104-1, 104-2... 104-N, collectively referred to as user 104 hereinafter, or applications residing on the user devices 104. Examples of the user devices 104 may include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation. The user devices 104 are communicatively coupled to the system 102 and the system 103 through a network 106. [0030] In one implementation, the network 106 may be a wireless network, a wired network or a combination thereof The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 106 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), TCP/IP, Wireless Application Protocol (WAP), 8 InfiniBand Protocol, Ethernet Protocol and the like to communicate with one another. Further the network 106 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like. [0031] Referring now to Figure 2, the system 102 is illustrated in accordance with an embodiment of the present subject matter. In one embodiment, the system 102 may include at least one processor 202, an input/output (I/O) interface 204, a network interface card (NIC) 206 coupled to the processor and a memory 208. The NIC is enabled for TCP/IP. Further, the NIC may be enabled for TCP/IP to transmit or to receive messages. The at least one processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 208. [0032] The I/O interface 204 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 204 may allow the system 102 to interact with a user directly or through the client devices 104. Further, the I/O interface 204 may enable the system 102 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 204 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 204 may include one or more ports for connecting a number of devices to one another or to another server. [0033] The memory 208 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 208 may include modules 210 and data 212. 9 [0034] The modules 210 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 210 may include a mapping module 214, an organizing module 216, a transmitting module 218 and other modules 220. The other modules 220 may include programs or coded instructions that supplement applications and functions of the system 102. [0035] The data 212, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 208. The data 212 may also include a system database 222, a messaging library 224, and other data 226. The other data 226 may include data generated as a result of the execution of one or more modules in the other modules 220. [0036] Referring now to Figure 3, the system 103 is illustrated in accordance with an embodiment of the present subject matter. In one embodiment, the system 103 may include at least one processor 302, an input/output (I/O) interface 304, a NIC 306 coupled to the processor and a memory 308. The at least one processor 302 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 302 is configured to fetch and execute computer-readable instructions stored in the memory 308. [0037] The I/O interface 304 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 304 may allow the system 103 to interact with a user directly or through the client devices 104. Further, the I/O interface 304 may enable the system 103 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 304 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 304 may include one or more ports for connecting a number of devices to one another or to another server. 10 [0038] The memory 308 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 308 may include modules 310 and data 312. [0039] The modules 310 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 310 may include a mapping module (314), a retrieving module (316), a reading module (318) and other modules 320. The other modules 320 may include programs or coded instructions that supplement applications and functions of the system 103. [0040] The data 312, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 310. The data 312 may also include a system database 322, a messaging library 324 and other data 132. The other data 132 may include data generated as a result of the execution of one or more modules in the other modules 320. [0041] In one implementation, at first, a user may use the client device 104 to access the system 102 via the I/O interface 204. The user may register them using the I/O interface 204 in order to use the system 102. The working of the system 102 may be explained in detail in Figures 2 and 3 explained below. The system 102 may be used for transmitting multiple messages hosted on at least one host node, in an inter process communication. [0042] In accordance with an embodiment, referring to figure 2, the system 102 comprises the network interface card (NIC) coupled to the processor to enable TCP/IP Protocol. Further, the NIC may be enabled for TCP/IP to transmit or to receive messages. The NIC is capable of executing TCP/IP commands from remote host. The TCP/IP may be supported on the NIC using Ethernet network to connect at least one host node acting as sender to the host node acting as a receiver. The TCP/IP may be 11 supported on the hardware networking technology such as Ethernet (10/100/1000MBd), Arcnet, ATM, FDDI, Fiber Channel, USB, HIPPI, FireWire (IEEE 1394), Token Ring, and serial lines. Network Interface Card (NIC) may be supported with 1 GbE or 10 GbE ports on the system 102 server. [0043] The system 102 further comprises the messaging library (224). The messaging library comprises one or more message-send and message-receive functions. Further, the message-send and message-receive functions may be linked and invoked by the message transmitting and receiving application processes. According to an exemplary embodiment, the TCP/IP protocol is implemented over Ethernet architecture, the Ethernet is used to transmit the messages and receive acknowledgements for transmit of the messages. [0044] Referring to figure 2, the system 102 comprises a mapping module configured to map each of a remote sender process to each of a FIFO sub-queue associated with the host node. The mapping module is further configured to map each remote sender process with corresponding remote receiving process associated with a receiving node. The mapping of each of a remote sender process to each of a FIFO sub-queue associated with the host node and mapping of each remote sender process with corresponding remote receiver process associated with a receiving node is done by using one or more memory mapped file. Remote Sender processes run on the host node acting as a transmitter or a sender. Number of remote sender processes in the system 102, may exceed the number of users by one. The main remote sender process creates remote sender process threads for each sub-queue and initializes their state. Thus there may be number of remote sender processes exceeding the number of users by one. Remote Sender processes are configured for watching incoming messages and updating the remote receiving processes on the receiving host node via TCP/IP protocol. Remote Sender processes are configured for updating the sub-queues of the transmitting host node to the sub-queues of the receiving host node via the remote receiver processes through TCP/IP protocol. Number of remote receiver processes on the receiving node may exceed the number of users by one. There may be a dedicated 12 remote receiver process for each user. The user can be a sender. The user can be a publisher. [0045] In accordance with an embodiment, referring to figure 2, the system 102 comprises the organizing module (216) configured to arrange the messages received from at least one user in the one or more FIFO sub-queue associated with the host node. Further, there may be a FIFO sub-queue dedicated for each user on the one or more host node. The one or more FIFO sub-queues are stored in one or more memory mapped files. The organizing module is configured to arrange the messages so received from each user in the FIFO sub-queue dedicated for each user. The user can be a sender. The user can be a publisher. The organizing module upon receiving the messages invokes a messaging library. The memory mapped file is stored in the memory 208. The number of memory mapped files created exceeds the number of users by one. One memory mapped file for the main queue and one each for the sub queues created per user. The memory mapped file contains the FIFO sub-queue which is used for sending and receiving messages. [0046] In accordance with an embodiment, referring to figure 2, the system 102 comprises a transmitting module configured to transmit the messages from each FIFO sub-queue associated with the host node to the corresponding remote receiver process associated with the receiving node using the corresponding remote sender process. There can be one or more users present in the system. There can be a sub queue dedicated for each user. One or more FIFO sub-queues are associated with a main queue where size of the main queue is equal to or greater than the sum of the size of all the sub-queues associated with the main queue. The remote sender processes transmits the message data using the TCP/IP protocol. The remote sender processes may transmit the message data using the TCP/IP protocol over Ethernet to the remote receiver processes from the receiving node. There may be a dedicated remote sender process for each user on the host node and there may be a dedicated remote receiver process for each user on the receiving node to receive the messages. [0047] In accordance with another embodiment, the system 102 further comprises one or more receiving node configured to receive the messages from one or 13 more sender host nodes. The system 102 may comprise Ethernet switch that connects transmitter / sender host node and the receiver host node. [0048] In one implementation, a user may use the client device 104 to access the system 103 via the I/O interface 304. The user may register them using the I/O interface 304 in order to use the system 103. The working of the system 103 may be explained in detail in Figures 4 and 5 explained below. The system 103 may be used for receiving multiple messages hosted on at least one host node, in an inter-process communication. [0049] In accordance with an embodiment, referring to figure 3, the system 103 comprises the NIC coupled to the processor to enable TCP/IP Protocol. Further, the NIC may be enabled for TCP/IP Protocol to transmit or to receive messages. The NIC is capable of executing TCP/IP commands from local or remote host. The TCP/IP is supported on the NIC using hardware networking technology such as Ethernet (10/100/1000MBd), Arcnet, ATM, FDDI, Fiber Channel, USB, HIPPI, FireWire (IEEE 1394), Token Ring, and serial lines to connect at least one host node acting as sender to the host node acting as a receiver. Network Interface Card (NIC) may be supported with 1 GbE or 10 GbE ports on the system 103 server. [0050] The system 103 further comprises the messaging library (324). The messaging library comprises one or more message-send and message-receive functions. Further, the message-send and message-receive functions may be linked and invoked by the message transmitting and receiving application processes. The message send and message-receive functions are stored in a TCP/IP socket library. The message sending and message receiving may be performed by using TCP/IP socket library. According to an exemplary embodiment, the TCP/IP Protocol is implemented over Ethernet architecture, the Ethernet architecture is used to receive the messages and provide acknowledgements for the receiving of the messages. The message sending and message receiving is performed by using TCP/IP socket library. [0051] Referring to figure 3, the system 103 comprises a mapping module 314 configured to map each of a remote receiver process to each of a FIFO sub-queue 14 associated with the receiving node. Further the mapping module is configured to map each remote receiver process with corresponding remote sender process associated with a sending node by using one or more memory mapped files. The number of memory mapped files created exceeds the number of users by one. The number of remote receiver processes created exceeds the number of users by one. The number of remote sending processes created exceeds the number of users by one. [0052] Referring to figure 3, the system 103 further comprises a retrieving module 316 configured to receive the multiple messages transmitted from one or more host nodes with at least one user via a remote receiver process dedicated for each user. The retrieving module is configured to arrange the messages so received in a FIFO sub-queue, wherein each FIFO sub-queue is dedicated for each user and is stored in a memory mapped file. The system 103 comprises one or more FIFO sub-queues which are associated with a main queue where size of the main queue is equal to or greater than the sum of the size of all the sub-queues associated with the main queue. The retrieving module upon receiving the messages invokes a messaging library. The receiving of the messages may be carried out by the remote receiver processes using the TCP/IP protocol over Ethernet. The user can be a sender. The user can be a publisher. The retrieving module is further configured to invoke a messaging library when it receives the messages. The receiving of the messages is carried out by one or more remote receiver processes using the TCP/IP socket library stored in the messaging library 314. The memory mapped file is stored in the memory 308. The number of memory mapped files created exceeds the number of users by one. One memory mapped file for the main queue and one each for the sub-queues created per user. The memory mapped file contains one or more FIFO sub-queue which is used for sending and receiving messages. [0053] Referring to figure 3, the system 103 further comprises a reading module 318 configured to read the multiple messages from each of the FIFO sub queue by using a round-robin technique in a FIFO mode. The reading module 318 facilitates the user of the system to read the messages sent by the sender. The sender can be a publisher and a user can be receiver or can be a subscriber. The system 103 15 further comprises one or more transmitting node configured to transmit the messages from one or more host nodes. The system 103 further may comprise Ethernet switch, wireless router or underlying hardware bridge that connects sending host node or transmitting host node and receiving host node. [0054] In accordance with an embodiment of the present disclosure, referring to figure 4 and figure 5 implementation of the present disclosure is explained. Traditionally the low latency messaging systems support single publishers or senders and one or more subscribers or receivers. However, when the messaging system has to support multiple senders or writers, the framework of the present disclosure implements the same in a seamless and lockless manner. The system 102 of the present disclosure comprises the main queue which is divided into as many sub-queues as the maximum number of users/senders provided at the time of system configuration. The sum of the sizes of the sub-queues does not exceed that of the main queue. All the other characteristics of the sub-queue are inherited from the main queue. [0055] As each user connects to the main queue, a sub-queue is assigned to each user to write. The writing or sending of messages to the sub-queue occurs seamlessly just like the user/sender experience of writing to the main queue. Thus the interface for the user/sender remains unchanged. The system on the receiving node for the reader of the queue executes a round robin read on all the sub-queues and read the data and the interface for the reader also remains unchanged. [0056] Referring to figure 4, the implementation of the present disclosure in configuration 1 is explained by way of an example. Let us consider that there are the senders Sender 1, Sender 2 and Sender 3 using the system 102 installed on the same host node. The senders are sending the messages to the same system installed on a Server 1. A configuration file is created on the Server 1 which specifies the number of senders to the queue. By way of an example, the minimum no of senders may be 2 the maximum no of senders may be 10. The maximum number of senders can be configured as per requirements at the time of development. For explanation purpose, let us take the number of senders as 3. A main queue is created by specifying the size of messages, the size of the queue, and the port on which the receiver should listen for 16 the incoming messages from the senders. By way of an example, let us consider the queue is created for a size of 300 messages. Since there are 3 senders, 3 smaller sub queues are created each of size 100 messages. The TP Address of the receiver node is specified along with the port number on which the receiver is waiting for the sender to connect and receive the messages. [0057] Further, the implementation of the disclosure on the receiving node is explained. Let us consider a receiver on the receiving Server 2 wherein system 103 is installed. A configuration file is created on the Server 2 which specifies the number of senders to the queue. By way of an example, the minimum no of senders may be 2 the maximum no of senders may be 10. As explained above, let us take the number of senders as 3 same as above. A main queue is created by specifying the size of messages, the size of the queue, and the port on which the receiver should listen for the incoming messages from the senders. By way of an example, let us consider the queue is created for a size of 300 messages same as explained above. Since there are 3 senders, 3 smaller sub-queues are created each of size 100 messages. [0058] Referring to figure 4, implementation of the present disclosure over TCP/IP supported network is explained. The implementation may involve two processes in the message transfer over TCP/IP, the Remote Sender Process (RS) and the Remote Receiver Process (RR). Remote Sender Processes and the Remote Receiver Process establish a TCP/IP socket connection at the time of the queue setup process. The Sender Process (S) can write to the local memory mapped queue file. The Remote Sender Process (RS) may transfer the data using the TCP/IP socket library call sendd) and the Remote Receiver Process (RR) may receive the data using the TCP/IP socket library call (recvo). [0059] Referring to figure 5, there can be multiple senders using the system 102 installed on different host nodes such as servers. Referring to figure 5, by way of an example there may be four users using system for transmitting multiple messages installed on different host nodes such as Server 1 and Server 2 respectively for Sender 1 and Sender 2 using Server 1 and Sender 3 and Sender 4 using the Server 2. Remote sender processes RS1, RS2 and RS3 and RS4 may set up TCP/IP connections directly 17 with the remote receiver processes RR1, RR2, RR3 and RR4 respectively. The remote receiver processes may set up the TCP/IP socket connection with the corresponding remote sender processes that connect for example RS1 and RS2 as shown in figure 5. [0060] By way of an example, referring to figure 5, in configuration 2, a configuration file is created on the Server 1 and Server 2 which specifies the number of senders to the queue. By way of an example, the minimum no of senders may be 2 the maximum no of senders may be 10. A main queue is created by specifying the size of messages, the size of the queue, and the port on which the receiver should listen for the incoming messages from the senders. By way of an example, let us consider, as explained above, there are 2 senders on each server, so a main queue of size 200 messages is created on each server having two sub-queues each of size 100 messages. Similar structures of main queue holding sub-queues are created on the receiver node that is on the Server 3 to receive and arrange the messages. This is important as the two sub-queues on either end have to be of the same size for uniformity and balance to be maintained. As part of the queue creation process the TP Address of the receiver is specified along with the port number on which the receiver is waiting for senders to connect. Further, it is to be noted that IP Address has to belong to a NIC card which supports TCP/IP transfer. Further, as explained above the transfer of the messages takes place over TCP/IP supported network as explained in above paragraph 0059. [0061] Referring to figure 4 and figure 5, in accordance with an exemplary embodiment, the detailed explanation of the implementation of transfer of messages is provided. The remote receiver processes are started first at the receiver end followed by the remote sender processes on the sender end. The remote receiver process knows the number of remote sender processes that are going to connect to it for its queue (as mentioned in paragraph 0060 above). At the receiver node, the remote receiver processes are started and mapped to the corresponding sub-queues by providing the memory mapped file address. The remote receiver processes initialize some state and wait for each sender's remote sender process to connect with it. The receiving processes listen on the port specified at queue creation. On the sender's system, a remote sender process is started for the multiple senders queue. The remote sender 18 process checks the number of senders on the system for the queue and spawns that many remote sender processes. [0062] So referring to figure 4, for Configuration 1, the remote receiver and remote sender processes connect using the TCP/IP protocol. The remote receiver process creates a TCP/IP socket using the socket() library call, binds the IP address and port number given at the time of queue creation using the bindo library call and listens on the socket listeno library call) for a remote sender process to connect to it. The remote sender process creates a TCP/IP socket using the socket library call and connects to the given IP address and port where the remote receiver process is listening using the connect() library call. On receiving a connect request from the remote sender process, the remote receiver process accepts the request using the accept() library call and the connection is established. At the time of queue creation, the port number is specified. The first remote receiver and the remote sender processes started use the specified port number, the next pair of processes use port number + 20, the next pair of processes use port number + 40 and so on. [0063] Referring to figure 4, for Configuration 1, on the sender's Server 1, a remote sender process is started, which in turn starts off three remote sender processes. Each remote sender process is assigned a sub-queue and connects with the corresponding remote receiver process on the receiver system. A TCP/IP socket connection is established on the user provided or system provided port. Referring to figure 5, for configuration 2, the remote sender process starts off two remote sender processes on each server so a total of four remote sender processes are started for four senders. [0064] Referring to figure 4, the sender's processes S1 and S2 are started with the name of the queue and the number of messages they want to send or publish. As each sender is started, it is assigned a sub-queue. The sender starts inserting messages into the sub-queue through respective sender processes, for example sender process S1 for Sender 1 and Sender process S2 for Sender 2. Further, the remote sender process reads the available messages in respective assigned sub-queue and transfers it to the corresponding receiver process on the receiver's system. As each transfer happens, the 19 remote receiver process receives the messages on the socket and inserts them into its corresponding sub-queue on the receiver's system. The receiver process then reads from all the sub-queues in a round robin fashion to read the messages from all the senders. If more senders than the number configured attempt to write to the queue, an error is returned and the extra sender exits. If there are lesser senders, then the remote sender process for the sub-queue continues to wait for a sender to start. The receiver processes checks each sub-queue and moves on if there are no messages in it. As each remote sender process reads the messages from corresponding sub-queue and transfers the messages on the TCP/IP socket, the corresponding remote sender process updates the header area of the sub-queue and the sender knows that the messages have been read and it continues writing fresh messages in its sub-queue. Once a sender exits, the sub-queue becomes available for assignment to another sender. [0065] Still referring to figure 4 and figure 5, in accordance with an embodiment of the present disclosure, the lockless mechanism is explained for multiple senders sending messages using system 102 and system 103 over the TCP/IP network in an inter process communication. The lockless mechanism is provided by way of allowing the plurality of senders to write messages to their assigned sub-queues without knowing presence of each other. The writing or sending of messages to the sub-queue occurs seamlessly just as the sender experience of writing to the main queue. Thus the interface for the sender remains unchanged. The system 103 on the receiving node for the receiver of the queue executes a round robin read on all the sub queues to read the data and the interface for the receiver also remains unchanged. Thus simultaneous writing of multiple senders without providing any locking to the queue and simultaneous reading of the messages on the receiver end is achieved through the system and method provided by the present disclosure. [0066] Referring to figure 6, the concept of main queue and sub-queue is described. At the time of queue creation, the configuration file is checked to identify whether the queue is a multi-senders queue. The configuration file also mentions the maximum number of senders that the queue may support. Further, at the time of 20 creation of the queue, the maximum size of messages, the length of the queue, the IP Address and port of the receiver among other parameters is also mentioned. [0067] The main queue is created with above mentioned parameters. The number of senders is extracted from the configuration file and the same numbers of sub-queues are created. The sub-queues inherit all the properties of the main queue but the length of the sub-queue is calculated as described below: Length of sub-queue = length of main queue/number of senders By way of an example, when the main queue is of length 300 and there are 3 senders, the length of each sub-queue is 100. By way of an example, the main queue is called IULTWRITE, and there are three senders, the sub-queues are named as MULTWRITE 0, MULTWRITE_1 and MULTWRITE_2. [0068] Further, the main queue also maintains an array of structures in which the name of each sub-queue and its status (whether currently allocated to a sender or unallocated) is stored. By maintaining the above mentioned information in the main queue, track of sub-queue is maintained and the sub-queue can be allocated to a sender as it joins the system and opens the queue. Further, when a sender finishes inserting messages and disconnects from the queue, the appropriate sub-queue is marked as unallocated. The sub-queues also contain the ID of the main queue for ease of access. [0069] When a sender wants to use the queue, it opens the queue IULTWRITE. The organizing module of the system 102 looks up for the sub-queue that is available and if available, organizing module of the system 102 allocates that to the sender. For instance in the example above if four senders attempt to open the main queue, sender 1 is allocated IULTWRITE_0, sender 2 is allocated IULTWRITE_1, sender 3 is allocated IULTWRITE_2 and the fourth sender gets an error message as all three sub-queues are allocated. All messages written by the senders are inserted into its sub-queue. Thus the main queue is not used for messages it is primarily used for book keeping. After the sender finishes inserting its messages, it disconnects from the framework. At that time, the sub-queue it was using is marked as unallocated. 21 [0070] According to an embodiment of the present disclosure, referring to figure 6, the structure of main queue and sub-queue is described. The structure of the main queue consists of a header portion. The header portion contains the queue name, queue ID, message size, queue size and other characteristics. The header portion further consists of sub structure called RH which is the Reader Header. Reader Header contains the data pointing element and the deletion counter. The data pointing element points to the next message to be read by the reader. The deletion counter is the number of elements or messages that are read by the reader. The header portion further consists of a sub structure called WH which is the Writer Header. The Writer Header contains the free pointing element and the insertion counter. The free pointing element points to the next location in which the writer can insert a message. The insertion counter is the number of elements or messages that are written by the writer. Further, SQ stands for sub-queue. This is the name of the sub-queue created under the main queue. 0 stands for occupied. This is true if the sub-queue has been assigned to a publisher. NO stands for not occupied. This is false if the sub-queue has not been allocated to a publisher. [0071] Still referring to figure 6, the fields mentioned in above paragraph belong to the structure of main queue and sub-queue. The queue comprises an array of structures. The size of the array is equal to the maximum number of senders to be supported. The array of structures is filled in the main queue and remains empty in the sub-queue. The reason is that the main queue is used to keep track of the sub-queues and track of the sub-queue that can be allocated to a sender. [0072] Still referring to figure 6, the significance of the RH and WH structures are explained. On the Sender's system, each Sender process inserts messages in its sub-queue and updates the variables in the WH structure of its sub-queue. The remote sender process of the sub-queue notices a change in these values and reads the inserted messages from the sub-queue, sends the messages on the TCP/IP socket and updates the RH structure of its sub-queue. This notifies the sender process that the messages are transferred to the reader and the sender process continues to insert fresh messages in the sub-queue. On the Receiver's system, each Remote Receiver process receives the messages sent by the corresponding remote sender process from the TCP/IP socket 22 and inserts them into its sub-queue. It updates the variables in the WH structure of the sub-queue. The receiver process notices the change in these values and reads the messages inserted into the sub-queue and updates the RH structure of the sub-queue. The change in the values of RH notifies the Remote receiver process that the reader process has consumed the messages and it can continue receiving the messages from the remote sender process on the TCP/IP socket. [0073] Still referring figure 6, in accordance with an exemplary embodiment, by way of an example the main queue is called as QTRANSFER. Let us assume that there are three publishers or senders to the main queue, so three sub-queues are created and they are called as Q TRANSFER_0, QTRANSFER_1 and QTRANSFER_2. The user issues a command to create a queue by the name QTRANSFER. As part of the call, the main queue is created and then the sub-queues are created. Each sub queue is one third the length of the main queue. All other properties of the main queue are inherited by the sub-queues. [0074] In accordance with an embodiment of the present disclosure, the detail information related to layout and working of main queue (queue), the memory mapped file, the remote sender process and the transmission and receiving of messages over TCP/IP supported network can be referred from the application 1546/MUM/2010. The layout and working of the sub-queue is similar to the main queue (queue). [0075] According to an embodiment of the present disclosure, the system 102 and system 103 comprises multiple senders and a single receiver using the framework with TCP/IP. For each sender process, a remote sender process is associated. By way of present example, for three senders on a single system, by way of an example there may be ten active processes including three sender's processes, three remote sender processes, three remote receiver processes and one receiver process. Further, the system also comprises a dormant remote sender process and a dormant remote receiver process. According to the system 102, 103 and method 700 and 800 of the present disclosure, the remote receiver process is started first. Let us call this the main remote receiver process. The remote receiver process starts off remote receiver processes for each sender. Thus if the number of senders to be supported on the server is three, three 23 remote receiver processes are started by the main remote receiver process. The main remote receiver process then becomes dormant. The three remote receiver processes are each allocated a sub-queue for which the remote receiver process receives messages. The remote receiver processes each initialize a TCP/IP socket as mentioned in [0063] and wait for the corresponding remote sender process to connect. Further, the Remote sender process is started on the sender's server. Let us call this as the main remote sender process. The main remote sender process starts of remote sender processes for each sender on the server. Thus if the number of senders to be supported on the server is three, three remote sender processes are started by the main remote sender process. The main remote sender process then becomes dormant. The three remote sender processes are each allocated a sub-queue. Then each remote sender process contacts the corresponding remote receiver process and creates a TCP/IP socket connection as mentioned in [0063] to communicate with each other. Thus each remote receiver process is contacted by the corresponding remote sender process and a TCP/IP socket communication channel is set up. [0076] Further, each remote sender process on the system 102, waits for the sender process to start inserting messages in its sub-queue by checking the position of the free pointing variable and the value of the insertion counter in the WH structure of the sub-queue header. When a change is noticed, the remote sender process constructs a message containing all the available messages in the sub-queue and sends on the TCP/IP socket using the send library call. The process of transmission is described in detail in patent application 1546/IUM/2010. Further the remote sender process updates the RH structure in the sub-queue to notify the sender process that the messages have been transferred to the receiver's system. [0077] According to an exemplary embodiment, the working of the present disclosure on TCP/IP supported network by using queue and sub-queue is explained. The Remote Receiver processes on the system 103, receive the messages sent on the TCP/IP sockets by the recv() library call. The process of receiving the messages is described in detail in patent application 1546/MUM/2010. The remote receiver process updates the WH structure in the sub-queue to notify the Receiver process that 24 messages are inserted in the queue. The receiver process checks the status of the free pointing variable and the value of the insertion counter in the WH structure of each of the sub-queue headers in a round robin manner. On noticing a change, the Receiver process reads the message from the sub-queue and updates the RH structure of the sub queue signaling to the remote receiver process that the message are consumed and further messages may be received from the TCP/IP socket and inserted in the sub queue. [0078] Referring now to Figure 7, a method 700 for transmitting multiple messages hosted on at least one host node, in an inter-process communication is shown, in accordance with an embodiment of the present subject matter. The method 700 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 700 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices. [0079] The order in which the method 700 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 700 or alternate methods. Additionally, individual blocks may be deleted from the method 700 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof However, for ease of explanation, in the embodiments described below, the method 700 may be considered to be implemented in the above described system 102. [0080] Referring to figure 7, the method (700) for transmitting multiple messages hosted on at least one host node, in an inter-process communication is 25 described. The method 700 comprises executing message-send and message-receive functions allowing multiple messaging simultaneously in a lockless manner by using TCP/IP protocol to transmit multiple user messages. In one implementation, the message-send and message-receive functions may be stored in messaging library 224 and may be invoked by the modules stored in the memory and are executed by the processor. TCP/IP protocol is supported by the NIC. [0081] In step 702, each of a remote sender process may be mapped to each of a FIFO sub-queue associated with the host node and in step 704, each remote sender process may be mapped to corresponding remote receiver processes associated with a receiving node by using one or more memory mapped files. In one implementation, the mapping of each of the remote sender process to each of the FIFO sub-queue associated with the host node and mapping of each remote sender process with corresponding remote receiver process associated with the receiving node by using one or more memory mapped files may be carried out by the mapping module 214. [0082] In step 706, messages received from at least one user may be arranged in the one or more FIFO sub-queue associated with the host node wherein each FIFO sub-queue may be dedicated for each user and may be stored in a memory mapped file. In one implementation, the receiving of the messages and arranging of the messages in FIFO sub-queue associated with the host node may be carried out by the organizing module 216. [0083] In step 708, the messages from each FIFO sub-queue associated with the host node may be transmitted to the corresponding remote receiver process associated with the receiver node by using the corresponding remote sender process. In one implementation, the transmission of the messages from each FIFO sub-queue associated with the host node to the corresponding remote receiving process associated with the receiver node using the corresponding remote sender process may be carried out by the transmitting module 218. The method 700 steps such as 702, 704, 706 and 708 comprising the mapping, the arranging and the transmitting is performed by means of the processor 202. The number of memory mapped files created may exceed the number users by one and the number of remote sender processes may exceed the 26 number of users by one. The number of remote receiver processes may exceed the number of users by one. The method 700 is executed on the TCP/IP supported network by using at least one network interface card (NIC). [0084] Referring now to Figure 8, a method 800 for receiving multiple messages hosted on at least one host node, in an inter-process communication is shown, in accordance with an embodiment of the present subject matter. The method 800 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 800 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices. [0085] The order in which the method 800 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 800 or alternate methods. Additionally, individual blocks may be deleted from the method 800 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof However, for ease of explanation, in the embodiments described below, the method 800 may be considered to be implemented in the above described system 103. [0086] Referring to figure 8, the method (800) for receiving multiple messages hosted on at least one host node, in an inter-process communication is described. The method 800 comprises executing message-send and message-receive functions allowing multiple messaging simultaneously in a lockless manner by using TCP/IP protocol to receive multiple user messages. In one implementation, the message-send and message-receive functions may be stored in messaging library 324 and may be 27 invoked by the modules 310 stored in the memory 308 and are executed by the processor 302. TCP/IP protocol is supported by the NIC. [0087] In step 802, each of a remote receiver process of the receiving node may be mapped to each FIFO sub-queue associated with the receiving node and in step 804 each remote receiver process may be mapped with corresponding remote sender process associated with a sending node by using one or more memory mapped files. In one implementation, the mapping of each of a remote receiver process of the receiving node to each FIFO sub-queue associated with the receiving node and mapping of each remote receiver process with corresponding remote sender process associated with a sending node by using one or more memory mapped files is carried by the mapping module 314. [0088] In step 806, the multiple messages transmitted from one or more host nodes with at least one user may be received and in step 808 the messages so received may be arranged in a FIFO sub-queue, wherein the FIFO sub-queue may be dedicated for each user and may be stored in a memory mapped file. In one implementation, the receiving of the multiple messages transmitted from one or more host nodes with at least one user and arranging of the messages so received in a FIFO sub-queue, wherein the FIFO sub-queue may be dedicated for each user may be carried out by the retrieving module 316. [0089] In step 810, the multiple messages from each of the FIFO sub-queue may be read by using a round-robin technique in a FIFO mode. In one implementation, the reading of the multiple messages from each of the FIFO sub-queue by using a round-robin technique in a FIFO mode may be carried out by the reading module 318. The method 800 steps 802, 804, 806, 808, 810 comprising the mapping, the receiving, the arranging and the reading are performed by means of the processor. The number of memory mapped files created may exceed the number users by one. The number of remote sender processes created may exceed the number of users by one. The number of remote receiver processes created may exceed the number of users by one. The user can be a sender. The user can be a publisher. The receiver can be a subscriber. The 28 method 800 may be executed on the TCP/IP Protocol supported network by at least one NIC. [0090] In accordance with an exemplary embodiment, referring to figure 10, the performance results of the system 102 and system 103 for multiple sender support in low latency FIFO messaging is provided. The systems tested for the throughput test are systems 102 and 103 working on Inter Process Communication (IPC) on Local messaging system and TCP/IP protocol as shown in figure 10. The system is called Custom Built Queue (CBQ) The throughput test results are provided. Throughput is the maximum speed with which messages can be exchanged between the publishers and subscribers or senders and receivers. Referring to figure 9, the test set up for the throughput test is shown. By way of an example, the Custom Built Queue (CBQ) has been implemented in C. Since the trading application used for throughput testing was implemented in Java, JNI (Java Native Interface) was used to call the native C code functions from the Java application. Referring to figure 10, the maximum throughput performance of the Multiple Publisher Custom Built Queue (CBQ) using both Java and C application programs for three publishers is provided. The publishers can be senders. The subscribers can be receivers. [0091] According to an exemplary embodiment of the present disclosure and by way of an example, referring to figure 10, in the throughput test, the publishers at Server 1 insert messages of size 512 bytes into the Multiple Publisher Custom Built Queue (CBQ). There is no think time between simultaneous messages. The system 103 at subscriber end on server 2 calculates the time to receive one million messages and calculates the throughput in messages per second (msgs/sec). The size of the Custom Built Queue (CBQ) is 30 messages. Publishers implemented in Java use ByteArray messages and those in C use string messages. The tests were conducted with all processes (3 publishers + 1 subscriber) on the same system (IPC), and with the publishers and subscribers (3 publishers + 1 subscriber) on different servers as shown in figure 9, connected by a 1 Gbps link (TCP-1G), a 10 Gbps link (TCP-1OG). Referring to figure 10, the throughput test results are provided. 29 [0092] In accordance with an exemplary embodiment, referring to figure 12, the latency test results of the system 102 and system 103 for multiple sender support in low latency FIFO messaging is provided. The systems tested for the latency test are systems 102 and 103 working on Inter Process Communication (IPC) on Local messaging system and TCP/IP protocol as shown in figure 12. Latency is the time taken for a message to travel to a receiver and the response to come back to the sender. Referring to figure 11, the test setup for the latency test is shown. By way of an example, three publishers on server 1 insert messages into the Multi Publisher Custom Built Queue (CBQ). Publisher can be a sender of messages. A timestamp is embedded into the message just before inserting the message. The subscriber on server 2 reads the message from the Multi Publisher CBQ and in turn publishes it on a point to point CBQ connected to a subscriber on server 1. This is a loopback. The subscriber can be a receiver of the messages. The subscriber on server 1 reads the message and calculates the difference in time between when the message was sent and when the message was received. This is the latency of the message. Referring to figure 12, an average value of the round trip latency for one million messages is calculated and reported in figure 12 for all three deployments. The messages are sent at a throughput rate of fifty thousand (50000) messages/sec. The CBQ size is 30 as stated before. [0093] In accordance with another exemplary embodiment, various TCP/IP throughput and corresponding latency statistics is described. Various TCP/IP throughput and corresponding latency statistics is described. Referring to figure 13, average round trip latency statistics for the Multiple Publisher CBQ using TCP/IP over TCP/IP socket library by way of system 102 and system 103 is shown. The latency test was conducted for different publisher throughput rates 50,000 msgs/sec, 100,000 msgs/sec and maximum throughput. Referring to figure 13, average round trip latency statistics for the Multiple Publisher CBQ using TCP/IP over TCP/IP socket library by way of system 102 and system 103 is shown. Max throughput indicates the test in which the publishers have zero think time between consecutive messages. For the max throughput test, the average value of the throughput of an individual publisher is mentioned in the graph. Measurements have been taken for 1, 3, 6 and 9 publishers. 30 The publishers were distributed across two servers in the tests for six and nine publishers. The publishers and subscriber have been implemented in Java. The publishers can be the senders of the messages. [0094] In accordance with another embodiment of the disclosure, the present disclosure provides support for multiple publishers without the use of locking mechanism to regulate the write access to same queue. High messaging performance is achieved by the present disclosed system(s) and method(s) on the commodity servers. By way of an example the high throughput messaging achieved is more than 650000 messages serviced per second by the subscriber with a single publisher and there is less than 10% degradation for every three publishers added. Further, less than 10% degradation can be explained by referring to figure 13 and the line which denotes max throughput. For 1 publisher the subscriber services messages at 680,000 msgs/sec, for 3 it is 633,000 msgs/sec (which is almost 210,000*3 = 630,000 msgs/sec), for 6 it is 662,000 msgs/sec which is almost (6*110,000 = 660,000 msgs/sec) and for 9 it is 595,000 msgs/sec which is almost (70,000*9 = 630,000 msgs/sec) Low latency messages are delivered across the network with the latencies below 1ms for simultaneous 9 publishers. Further, present disclosure extends the multiple publisher features to both local and remote messaging systems. [0095] According to an exemplary embodiment, the Information about the Network Card used for the throughput, latency and TCP/IP tests is provided in Table 1 below. NetEfftedNE020 I 0GbAcceleraed Ethemet Adapter MWARP RNIC) (rev LS) 1ts0 G'Ps fatel Ccrportion825EBE1& O-Gigabit AF Dual Port NetVGkCernsedisnr(reV:1) EThemnet E~roadcom CorporaionNetX reme I 1 Gbps BCM5709G-abit Etheet (rae2Q) Table 1 31 [0096] According to an exemplary embodiment, the hardware configuration of the servers of the system 102 and system 103 used for the throughput, latency and TCP/IP tests is provided in Table 2 below. Socket Type nte Xeon CPU E56.20 CPU Freqercy 2A0 GH Cache Per Sccket 12 ME. Number of Sockets 2 Cores per socket physical3 4 SMT Enabled Cores per socket threata ds L9 RAM 1 G9 @ 133 MHz umx kem.e| rertflC 6,1 Red Hat Reease 2- .32-1,15e&x36 64 Table 2 32

Claims

1. A system for transmitting multiple messages hosted on at least one host node, in an inter-process communication, the system comprising: a processor; a Network Interface Card (NIC) coupled to the processor, wherein the Network Interface Card is enabled for Transmission Control Protocol / Internet Protocol to send the messages; a message library comprising one or more message-send and message receive functions allowing multiple messaging simultaneously in a lockless manner; and a memory coupled to the processor, wherein the processor is capable of executing a plurality of modules stored in the memory, the plurality of modules comprising: a mapping module configured to map each of a remote sender process to each of a FIFO sub-queue associated with the host node and mapping each remote sender process with corresponding remote receiver process associated with a receiving node by using one or more memory mapped files; an organizing module configured to arrange messages received from at least one user in the one or more First In First Out (FIFO) sub queue associated with the host node; wherein the FIFO sub-queue is dedicated for each user and is stored in a memory mapped file; and a transmitting module configured to transmit the messages from each FIFO sub-queue associated with the host node to the corresponding remote receiver process associated with the receiving node using the corresponding remote sender process. 33

2. The system of claim 1, wherein one or more FIFO sub-queues are associated with a main queue where size of the main queue is equal to or greater than the sum of the size of all the sub-queues present in the system.

3. The system of claim 1, wherein the organizing module upon receiving the messages invokes a messaging library.

4. The system of claim 1, wherein the user can be a sender.

5. The system of claim 1, wherein the sender process transmits the message data using the TCP/IP socket library.

6. The system of claim 1, wherein the number of memory mapped files created exceeds the number of users by one and number of remote sender processes exceeds the number of users by one.

7. The system of claim 1, wherein the Transmission Control Protocol / Internet Protocol is supported on the Network Interface Card using Ethernet, wireless LAN, ARCnet to connect at least one host node acting as sender to the host node acting as a receiver.

8. The system of claim 1, further comprises one or more receiving node configured to receive the messages from one or more sender host nodes.

9. The system of claim 1, wherein the transmitting host node and the receiving host node is connected by Ethernet switch or wireless router or hardware bridge .

10. A system for receiving multiple messages hosted on at least one host node, in an inter-process communication, the system comprising: a processor; a network interface card (NIC) coupled to the processor, wherein the network interface card is enabled for Transmission Control Protocol / Internet Protocol to receive messages; 34 a messaging library comprising one or more message-send and message-receive functions allowing multiple messaging simultaneously in a lockless manner; and a memory coupled to the processor, wherein the processor is capable of executing plurality of modules stored in the memory, the plurality of modules comprising: a mapping module configured to map each of a remote receiver process to each of a FIFO sub-queue associated with the receiving node and mapping each remote receiver process with corresponding remote sender process associated with a sending node by using one or more memory mapped files; a retrieving module configured to receive the multiple messages transmitted from one or more host nodes with at least one user via a remote receiver processes dedicated for each user, the messages so received are arranged in a First In First Out (FIFO) sub-queue, wherein each FIFO sub-queue is dedicated for each user and is stored in a memory mapped file; and a reading module configured to read the multiple messages from each of the FIFO sub-queue by using a round-robin technique in a FIFO mode.

11. The system of claim 10, wherein one or more FIFO sub-queues are associated with a main queue where size of the main queue is equal to or greater than the sum of the size of all the sub-queues present in the system.

12. The system of claim 10, wherein the retrieving module upon receiving the messages invokes a messaging library. 35

13. The system of claim 10, wherein the receiving of the messages is carried out by the remote receiver processes using Transmission Control Protocol/Internet Protocol socket library.

14. The system of claim 10, wherein the number of memory mapped files created exceeds the number of users by one.

15. The system of claim 10, wherein the number of receiving processes created exceeds the number of users by one.

16. The system of claim 10, wherein the Transmission Control Protocol / Internet Protocol is supported on the Network Interface Card using Ethernet or wireless LAN or ARCnet to connect at least one host node acting as sender to the host node acting as a receiver.

17. The system of claim 10, further comprises one or more transmitting node configured to transmit the messages from one or more host nodes.

18. The system of claim 10, wherein the transmitting host node and the receiving host node is connected by Ethernet switch or Wireless router or Hardware bridge.

19. A method for transmitting multiple messages hosted on at least one host node, in an inter-process communication, the method comprising: executing message-send and message-receive functions allowing multiple messaging simultaneously in a lockless manner; transmitting multiple user messages using Transmission Control Protocol / Internet Protocol; the transmitting further comprises: mapping each of a remote sender process to each of a FIFO sub queue associated with the host node and mapping each remote sender process with corresponding remote receiver process associated with a receiving node by using one or more memory mapped files; 36 arranging messages received from at least one user in the one or more First In First Out (FIFO) sub-queue associated with the host node; wherein the FIFO sub-queue is dedicated for each user and is stored in a memory mapped file; and transmitting the messages from each FIFO sub-queue associated with the host node to the corresponding each remote receiver process associated with the receiving node using the corresponding remote sender process; wherein the mapping, the arranging and the transmitting is performed by means of the processor.

20. The method of claim 19, wherein the number of memory mapped files created exceeds the number users by one and the number of remote sender processes exceeds the number of users by one.

21. The method of claim 19, wherein the method is executed on the Transmission Control Protocol / Internet Protocol supported network by at least one network interface card (NIC).

22. A method for receiving multiple messages hosted on at least one host node, in an inter-process communication, the method comprising: executing message-send and message-receive functions allowing multiple messaging simultaneously in a lockless manner; receiving multiple user messages using Transmission Control Protocol / Internet Protocol; the receiving further comprises: mapping each of a remote receiver process to each of a FIFO sub queue associated with the receiving node and mapping each remote receiver process with corresponding remote sender process associated with a sending node by using one or more memory mapped files; receiving the multiple messages transmitted from one or more host nodes with at least one user via a remote receiver processes dedicated 37 for each user, the messages so received are arranged in a First In First Out (FIFO) sub-queue, wherein each FIFO sub-queue is dedicated for each user and is stored in a memory mapped file; and reading the multiple messages from each of the FIFO sub-queue by using a round-robin technique in a FIFO mode; wherein the mapping, the receiving, the arranging and the reading is performed by means of the processor.

23. The method of claim 22, wherein the number of memory mapped files created exceeds the number of users by one.

24. The method of claim 22, wherein the number of remote receiver processes and the number of remote sender processes created exceeds the number of users by one.

25. The method of claim 22, wherein the user can be a sender.

26. The method of claim 22, wherein the method is executed on the Transmission Control Protocol / Internet Protocol supported network by at least one network interface card (NIC). 38