Method for storing an application's transaction data in a wireless messaging system
A method for storing transaction data for an application in a wireless messaging system is disclosed. Applications can be used to allow paging messages to be entered into a wireless messaging system from external systems such as E-mail or the World Wide Web. Such applications may be implemented on a...
Gespeichert in:
Hauptverfasser: | , |
---|---|
Format: | Patent |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | A method for storing transaction data for an application in a wireless messaging system is disclosed. Applications can be used to allow paging messages to be entered into a wireless messaging system from external systems such as E-mail or the World Wide Web. Such applications may be implemented on an external application platform that includes the hardware system and system software required by the application. Applications often require the use of certain type of transaction data that has traditionally been stored in an application database designed specifically for this purpose by an application developer. The present invention provides a method for storing such transaction data without requiring the application developer to create a separate database. In the past, the development of such databases has been a significant burden on application developers. The present invention allows the application to store the necessary transaction data in a database inside the wireless messaging system, through the use of a code library that allows the application to send special networking messages to the wireless messaging system. In a hybrid system, the application may still have its own transaction database in which to store some types of transaction data, but may store other types of transaction data in a database in the wireless messaging infrastructure. The application's transaction database in these hybrid systems is simpler to design than those that store all the transaction data for the application. |
---|