Message handling multiplexer

• US 20080298363A1
• Filed: 05/29/2007
• Published: 12/04/2008
• Est. Priority Date: 05/29/2007
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Ban, Bela, Blagojevic, Vladimir
• Granted Patent: US 8,611,378 B2
• Time in Patent Office: Days
• US Class Current: 370/390
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• CPC Class Codes: H04L 49/90 Buffering arrangements

Abstract

A method and apparatus for processing message is described. In one embodiment, an application programming interface is configured for receiving and sending messages. A multiplexer receives messages from different servers. A service name is coupled to each message with the corresponding destination service. A single shared channel is formed. The messages are processed over the single shared channel.

Claims

1. A computer-implemented method for processing messages, the method comprising:

receiving messages from a plurality of servers;

coupling a service name to each message with the corresponding destination service;

forming a single shared channel; and

processing the messages over the single shared channel.

2. The method of claim 1 wherein processing further comprises:

multiplexing the messages onto the single shared channel; and

sending the messages over the single shared channel.

3. The method of claim 1 wherein processing further comprises:

determining the service name for each message from the single shared channel; and

channeling each message to the corresponding service based on the service name of each message.

4. The method of claim 1 further comprising:

forming a thread pool to concurrently dispatch messages to different services from a same server.

5. The method of claim 4 further comprising:

processing one thread for messages to a same service from the same server.

6. The method of claim 1 wherein receiving packets further comprises:

receiving packets with a transport protocol stack, the transport protocol comprising a multicast receiver thread, a unicast receiver thread, or a connection table.

7. The method of claim 6 wherein the thread sends the messages up the transport protocol stack to a corresponding channel of a channel layer, a building block layered on top of the channel layer, and an application programming interface layered on top of the building block.

8. An article of manufacture comprising:

a machine-accessible storage medium including data that, when accessed by a machine, cause the machine to perform a method comprising;

receiving messages from a plurality of servers;

coupling a service name to each message with the corresponding destination service;

forming a single shared channel; and

processing the messages over the single shared channel.

9. The article of manufacture of claim 8 wherein processing further comprises:

multiplexing the messages onto the single shared channel; and

sending the messages over the single shared channel.

10. The article of manufacture of claim 8 wherein processing further comprises:

determining the service name for each message from the single shared channel; and

channeling each message to the corresponding service based on the service name of each message.

11. The article of manufacture of claim 8 further comprising:

forming a thread pool to concurrently dispatch messages to different services from a same server.

12. The article of manufacture of claim 11 further comprising:

processing one thread for messages to a same service from the same server.

13. The article of manufacture of claim 8 wherein receiving packets further comprises:

receiving packets with a transport protocol stack, the transport protocol comprising a multicast receiver thread, a unicast receiver thread, or a connection table.

14. The article of manufacture of claim 13 wherein the thread sends the messages up the transport protocol stack to a corresponding channel of a channel layer, a building block layered on top of the channel layer, and an application programming interface layered on top of the building block.

15. An apparatus for processing messages comprising:

an application programming interface for receiving and sending messages;

a building block layer coupled to the application programming interface;

a multiplexer coupled to the building block;

a channel layer coupled to the multiplexer; and

a transport protocol stack coupled to the channel layer for implementing properties specified by the channel layer,

wherein the multiplexer is to receive messages from a plurality of servers, to couple a service name to each message with the corresponding destination service, to form a single shared channel, and to process the messages over the single shared channel.

16. The apparatus of claim 15 wherein the multiplexer is to further multiplex the messages onto the single shared channel, and to send the messages over the single shared channel.

17. The apparatus of claim 15 wherein the multiplexer is to further determine the service name for each message from the single shared channel, and to channel each message to the corresponding service based on the service name of each message.

18. The apparatus of claim 15 wherein the multiplexer is to further form a thread pool to concurrently dispatch messages to different services from a same server.

19. The apparatus of claim 18 wherein the multiplexer is to further process one thread for messages to a same service from the same server.

20. The apparatus of claim 15 wherein the transport protocol stack comprises a multicast receiver thread, a unicast receiver thread, or a connection table, and a concurrent stack consisting of an out of band thread pool and a regular thread pool, the regular thread pool to form one thread for every messages from a sender, and the out of band thread pool to form one thread for messages marked as out of band from the sender, wherein messages processed with the thread from the out of band thread pool are processed before messages processed with the regular thread pool.