SMART JMS NETWORK STACK

• US 20100070650A1
• Filed: 11/29/2007
• Published: 03/18/2010
• Est. Priority Date: 12/02/2006
• Status: Abandoned Application

• Current Assignee: Metafluent LLC
• Original Assignee: Metafluent LLC
• Inventors: MacGaffey, Andrew, Lankford, Peter
• Application Number:
  US12/312,836
• Publication Number:
  US 20100070650A1
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields

Abstract

In a client server network, the invention provides improved message routing, useful in sending a plurality of subscriber messages from a single Server published message. The invention provides all the benefits of TCP delivery with most of the efficiency of IP multicast delivery. The invention provides for a Controller associated in the Client Server communication, where the Controller effectively routes the Server message to subscribed Clients. The invention provides efficient distribution of streaming data to one or more consumers in a way that enables easy integration in consuming applications. The invention provides means to implement a Java Message Service (JMS) distribution adapter in hardware. The invention further provides for hardware implementation of various wire protocol transforms.

Claims

1. In a client server network, wherein one or more Clients request subscription-based messages from at least one Servers, a message distribution system comprising:

at least one Server said Server including Server Application and at least one Controller implemented via a network adapter, in communication with server and server application;

at least one switch, and

at least one Client, said client including an API, operable to communicate with said Server, such that in operation said Server writes a single message, and said Controller implements routing of said server message to one or more eligible Clients.

2. The message distribution system as in claim 1, where the API is JMS.

3. The message distribution system as in claim 1 wherein the Controller is a network adapter compatible with commercially available network media such as Ethernet switches and Infiniband switches.

4. The message distribution system as in claim 1 wherein more than one Controller is associated with a Server, providing increased fan-out of messages to Clients.

5. In a client server network wherein one or more Clients request subscription-based messages from at least one Server, a message distribution system comprising:

at least one Server said Server including server application TCP/IP protocol stack, and a Network Interface Card (NIC),

at least one Controller containing logic sufficient to maintain subscription tables and perform Topic to Client routing; and

at least one Client, said Client including an API, TCP/IP protocol stack, and NIC operable to communicate with said Server though said Controller, such that said Controller receives Topics from Server via TCP/IP and said Controller, using TCP/IP, forwards said Topic to one or more eligible Clients.

6. The message distribution system as in claim 5, where the API is JMS.

7. The message distribution system as in claim 5, wherein the Controller is a switch operable to deliver a message from the Server by one or more switching methods, including route processors, interface processors, dedicated ASICs.

8. In a client server network wherein one or more Clients request subscription-based messages from at least one Server, a message distribution system comprising:

at least one Server said Server including server application, Server High Performance Computing (HPC) protocol based interconnect stack, and a Server proprietary NIC;

at least one Controller containing logic sufficient to maintain subscription tables and perform Topic to Client routing; and

at least one Client, said Client including an API, Client proprietary NIC, a Client HPC protocol based interconnect stack, and System memory, said Client operable to communicate with said Server though said Controller, such that said Controller receives Topics from Server via HPC interconnects and said Controller forwards said Topics to one or more eligible Clients.

9. The message distribution system as in claim 8, where the API is JMS.