Buffering enterprise messages

• US 20050262215A1
• Filed: 04/30/2004
• Published: 11/24/2005
• Est. Priority Date: 04/30/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Koegel, Michael, Kirov, Margarit P., Nikolov, Radoslav I., Follmeg, Bernd
• Granted Patent: US 7,640,357 B2
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]

Abstract

Methods and apparatuses for buffering enterprise messages are described herein. In one embodiment, an exemplary process is provided to transmit, from a messaging server to a client, a first message indicating a size of a next enterprise message to be sent to the client. A second message is received from the client in response to the first message, where the second message indicates a buffer size available to store messages for the client. The next enterprise message is then delivered to the buffer of the client if the size of the next enterprise message is smaller than or equal to the size of the available buffer of the client. Other methods and apparatuses are also described.

Claims

1. A method for processing messages in an enterprise computing environment, the method comprising:

transmitting, from a messaging server to a client, a first message indicating a size of a next enterprise message to be sent to the client;

receiving a second message from the client in response to the first message, the second message indicating a buffer size available to store messages for the client; and

sending the next enterprise message to the buffer of the client if the size of the next enterprise message is smaller than or equal to the size of the available buffer of the client.

2. The method of claim 1, further comprising:

determining the size of the available buffer of the client based on an amount of data previously sent to the client; and

performing transmitting the first message to the client if the determined size of the available buffer of the client is smaller than the size of the next enterprise message.

3. The method of claim 1, further comprising deducting the size of the next enterprise message from the buffer size available to receive messages of the client.

4. The method of claim 1, wherein the messaging server is a Java messaging service (JMS) compatible provider.

5. The method of claim 3, wherein the client is a JMS compatible consumer.

6. The method of claim 3, wherein the next enterprise message is associated with a topic produced by a producer coupled to the JMS provider and subscribed by the client.

7. A machine-readable medium when executed by a processor, causes the processor to perform a method for processing messages, the method comprising:

transmitting to a client a first message indicating a size of a next enterprise message to be sent to the client;

receiving a second message from the client in response to the first message, the second message indicating a buffer size available to store messages for the client; and

sending the next enterprise message to the buffer of the client if the size of the next enterprise message is smaller than or equal to the size of the available buffer of the client.

8. The machine-readable medium of claim 7, wherein the method further comprises:

determining the size of the available buffer of the client based on an amount of data previously sent to the client; and

performing transmitting the first message to the client if the determined size of the available buffer of the client is smaller than the size of the next enterprise message.

9. The machine-readable medium of claim 7, wherein the method further comprises deducting the size of the next enterprise message from the buffer size available to receive messages of the client.

10. The machine-readable medium of claim 7, wherein the messaging server is a Java messaging service (JMS) compatible provider.

11. The machine-readable medium of claim 10, wherein the client is a JMS compatible consumer.

12. The machine-readable medium of claim 10, wherein the next enterprise message is associated with a topic produced by a producer coupled to the JMS provider and subscribed by the client.

13. An enterprise messaging system, comprising:

a processor;

a memory coupled to the processor; and

a process when executed from the memory, causes the processor to

transmit to a client a first message indicating a size of a next enterprise message to be sent to the client,

receive a second message from the client in response to the first message, the second message indicating a buffer size available to store messages for the client, and

send the next enterprise message to the buffer of the client if the size of the next enterprise message is smaller than or equal to the size of the available buffer of the client.

14. A method for processing messages in an enterprise computing environment, the method comprising:

receiving a first message from a server indicating a size of a next enterprise message pending to be delivered;

determining whether a size of a buffer available to receive messages is greater than or equal to the size of the next enterprise message; and

transmitting a second message to the server to start receiving the next enterprise message if the size of the buffer available to receive messages is greater than or equal to the size of the next enterprise message,

wherein the second message includes the size of the buffer available to receive messages and the second message is used by the server to determine whether to deliver the next enterprise message.

15. The method of claim 14, wherein if the size of the buffer available to receive messages is less than the size of the next enterprise message, the method further comprises:

dynamically allocating an additional buffer that is large enough to receive the next enterprise message; and

transmitting a third message to the server to start receiving the next enterprise message, the third message including the size of the additional buffer.

16. The method of claim 15, wherein if the additional buffer is unsuccessfully allocated, the method further comprises suspending transmitting the third message to the server until the additional buffer is successfully allocated.

17. The method of claim 15, further comprising:

receiving the next enterprise message from the server using the additional buffer; and

releasing the additional buffer after the next enterprise message has been delivered to a consumer.

18. The method of claim 15, wherein the additional buffer is allocated from a pool of memories shared among a plurality of consumers.

19. The method of claim 14, wherein the messaging server is a Java message service (JMS) compatible provider.

20. The method of claim 19, wherein the client is a JMS compatible consumer.

21. The method of claim 14, wherein the next enterprise message is associated with a topic published by a produced coupled to the JMS provider and the client is a subscriber to the topic.

22. A machine-readable medium when executed by a processor, causes the processor to perform a method for processing messages, the method comprising:

receiving a first message from a server indicating a size of a next enterprise message pending to be delivered;

determining whether a size of a buffer available to receive messages is greater than or equal to the size of the next enterprise message; and

transmitting a second message to the server to start receiving the next enterprise message if the size of the buffer available to receive messages is greater than or equal to the size of the next enterprise message,

wherein the second message includes the size of the buffer available to receive messages and the second message is used by the server to determine whether to deliver the next enterprise message.

23. The machine-readable medium of claim 22, wherein if the size of the buffer available to receive messages is less than the size of the next enterprise message, the method further comprises:

dynamically allocating an additional buffer that is large enough to receive the next enterprise message; and

transmitting a third message to the server to start receiving the next enterprise message, the third message including the size of the additional buffer.

24. The machine-readable medium of claim 23, wherein if the additional buffer is unsuccessfully allocated, the method further comprises suspending transmitting the third message to the server until the additional buffer is successfully allocated.

25. The machine-readable medium of claim 23, wherein the method further comprises:

receiving the next enterprise message from the server using the additional buffer; and

releasing the additional buffer after the next enterprise message has been delivered to a consumer.

26. The machine-readable medium of claim 23, wherein the additional buffer is allocated from a pool of memories shared among a plurality of consumers.

27. The machine-readable medium of claim 22, wherein the messaging server is a Java message service (JMS) compatible provider.

28. The machine-readable medium of claim 27, wherein the client is a JMS compatible consumer.

29. The machine-readable medium of claim 22, wherein the next enterprise message is associated with a topic published by a produced coupled to the JMS provider and the client is a subscriber to the topic.

30. An enterprise messaging system, comprising:

a processor;

a memory coupled to the processor; and

a process when executed from the memory, causes the processor to

receive a first message from a server indicating a size of a next enterprise message pending to be delivered,

determine whether a size of a buffer available to receive messages is greater than or equal to the size of the next enterprise message,

transmita second message to the server to start receiving the next enterprise message if the size of the buffer available to receive messages is greater than or equal to the size of the next enterprise message, and

wherein the second message includes the size of the buffer available to receive messages and the second message is used by the server to determine whether to deliver the next enterprise message.