Asynchronous message delivery system and method

• US 20030115366A1
• Filed: 12/18/2001
• Published: 06/19/2003
• Est. Priority Date: 12/18/2001
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Robinson, Brian R.
• Application Number:
  US10/023,590
• Publication Number:
  US 20030115366A1
• Time in Patent Office: Days
• US Class Current: 709/248
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication

Abstract

The present invention comprises a method for delivering message data in an asynchronous messaging system. The method comprises specifying message data in a custom tag to be sent to a client from a server page, the server page that comprises a scripting language and extensible custom tag functionality, and the client operable to receive asynchronous messages. The method also comprises specifying attributes to be used with the tag to send the message data to one of a queue and a topic, and automatically delivering the message data to the one of the queue and the topic in the client upon execution of the server page. In a particular embodiment, the attributes are specified by using JNDI.

Claims

1. A method for delivering message data in an asynchronous messaging system, comprising:

specifying message data in a custom tag to be sent to a client from a server page, that comprises a scripting language and extensible custom tag functionality, and the client operable to receive asynchronous messages;

specifying attributes to be used with the tag to send the message data to one of a queue and a topic; and

automatically delivering the message data to the one of the queue and the topic in the client upon execution of the server page.

2. The method of claim 1, wherein the client is a wireless device.

3. The method of claim 1, further comprising specifying the attributes by using the attributes to identify an instance of a software class to be obtained by using an interface distributed under the name JNDI.

4. The method of claim 1, further comprising specifying the attributes by using the attributes to identify an instance of a software class to be created usingreflection.

5. The method of claim 1, further comprising specifying the attributes as deliveryMode, priority, and timeToLive.

6. The method of claim 1, wherein the scripting language comprises software code implemented by employing the language distributed under the name JAVA.

7. The method of claim 1, wherein the asynchronous messaging system comprises software code that is distributed under the name JAVA Message Service.

8. A system for delivering message data in an asynchronous messaging system, comprising:

a server; and

application software operatively associated with the server and operable to

execute a server page that comprises a scripting language and extensible custom tag functionality; and

cause automatic delivery of the message data to one of a queue and a topic upon execution of the server page; and

wherein the message data is encoded in a custom tag in the server page, and the tag uses attributes to specify a destination of the message data to the one of the queue and the topic.

9. The system of claim 8, further comprising a client coupled to the server and operable to receive asynchronous messages and the message data.

10. The system of claim 8, wherein the topic and the queue reside on the server.

11. The system of claim 8, wherein the topic and the queue reside on a second server.

12. The system of claim 8, further comprising a JSP server resident on the server, the JSP server operable to send the message data to the queue or the topic.

13. The system of claim 8, further comprising a JSP server resident on a second server, the JSP server operable to send the message data to the queue or the topic.

14. The system of claim 8, wherein the attributes comprise deliveryMode, priority, and timeToLive.

15. The system of claim 8, wherein the attributes identify an instance of one of the group consisting of a software class to be created using reflection and a software class to be obtained using an interface distributed under the name JNDI.

16. The system of claim 8, wherein the scripting language comprises software code implemented by employing the language distributed under the name JAVA.

17. The system of claim 8, wherein the asynchronous messaging system comprises software code that is distributed under the name JAVA Message Service.

18. A system for receiving message data, comprising:

a client operable to receive asynchronous messages; and

a message retrieval application programming interface operatively associated with the client and operable to retrieve message data from one of a queue and a topic; and

wherein the message data is encoded in a custom tag in a server page that comprises a scripting language and extensible custom tag functionality and is automatically delivered to the one of the queue and the topic upon execution of the server page.

19. The system of claim 18, wherein the custom tag uses attributes to specify a destination of the message data to the one of the queue and the topic.

20. The system of claim 19, wherein the attributes comprise deliveryMode, priority, and timeToLive.

21. The system of claim 18, wherein the client is a wireless device.

22. The system of claim 18, wherein additional message data is encoded in the custom tag and is automatically delivered to the one of the queue and the topic upon execution of the server page.

23. The system of claim 18, wherein at least one of the topic and the queue reside on a server coupled to the client.

24. The system of claim 18, wherein the attributes identify an instance of a software class to be created usingreflection.

25. The system of claim 18, wherein the attributes identify an instance of a software class to be obtained using an interface distributed under the name JNDI.

26. The system of claim 18, wherein the message retrieval application programming interface comprises a browser.

27. The system of claim 18, wherein the scripting language comprises software code implemented by employing the language distributed under the name JAVA.

28. The system of claim 18, wherein the asynchronous messaging system comprises software code that is distributed under the name JAVA Message Service.