Abstract: To enable use of an application on an application server at a mobile communication device, at a transaction server, a message received from the mobile is pushed out to the application. Any return messages is routed back to the mobile. The transaction server may use a queue to store all messages destined to a given application and attempt to push all messages on a given queue on receipt of a further message for the queue.

Abstract: A new master application definition is installed at a server. Responsively, the server determines the identity of a user associated with the server-side application related to the master application definition. The server may then generate an application definition file specific to the application and to the remote wireless device associated with the identified user. The application definition file may contain definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the server-side application and formatted in accordance with the definitions. The wireless device may then present a user interface for the application. Preferably, the application definition file is an XML file. Advantageously, when changes occur to previously established server-side applications, automatic updating of devices is efficiently accomplished.

Abstract: To enable use of an application on an application server at a mobile communication device, at a transaction server, a message received from the mobile is pushed out to the application. Any return messages is routed back to the mobile. The transaction server may use a queue to store all messages destined to a given application and attempt to push all messages on a given queue on receipt of a further message for the queue.

Abstract: A remote wireless device receives a compressed message including an application definition file. The application definition file is associated with an application executing at a computing device and contains definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the application and formatted in accordance with the definitions. The wireless device may then present a user interface for the application. Preferably, the application definition file is an XML file. Similarly, application-specific network messages provided to the device are also formed using XML. Data generated by the application may be presented at the mobile device under control of a virtual machine that uses the application definition file. For efficiency, the network messages received at, and transmitted by, the wireless device may be compressed.

Abstract: Software, methods and devices for executing textually-defined instructions at a wireless communication device are disclosed. The instructions may be for performing a mathematical operation upon specified integer or floating-point operands, for performing one or more specified actions for each pass through a loop, for performing one of two sets of actions based on a user selection of one of two user interface controls, or for triggering a timer for delaying a subsequent action by a specified time interval. The instructions may be defined in a markup language such as Extensible Markup Language (XML). The software, methods and devices may form part of a system for allowing varied wireless communication devices to interact with server-side software applications.

Abstract: Responsive to the sensing of an occurrence of an event, an action may be executed according to which a message is generated. The message may be generated with a format that is based on an application definition document. According to the application definition document, a label may be generated for associating with the message. The message and label may then be stored in a queue in a manner that allows the label to be associated with the message. Subsequent to the message having been stored, a representation of the queue may be displayed for review by a user interested in the status of the message, or the queue in general. The label associated with the message is displayed in the representation rather than the actual code of the message, thereby allowing the viewer of the display to make an informed decision regarding further activity to carried out on the message.

Abstract: A markup language document (e.g. an XML document) may contain a first instance of a markup language element having an attribute with a first, platform-independent value, a second instance of the element having the attribute with a second, platform-specific value, and an indicator that the second value overrides the first. Executable code may replace both of the first and second instances with a single instance having the attribute with the second value. Alternatively the markup language document may contain a first instance of a markup language element having a first, platform-independent attribute, a second instance of the element having a second, platform-specific attribute different from the first attribute, and an indicator that the second instance extends the first. In this case executable code may replace both instances of the markup language element with a single instance having the first attribute and the second attribute.

Abstract: A remote wireless device registers with a server. Responsively, the server determines the identity of a server-side application associated with a user of the remote wireless device. The server may then generate an application definition file specific to the server-side application and to the remote wireless device. The application definition file may contain definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the server-side application and formatted in accordance with the definitions. The wireless device may then present a user interface for the server-side application. The application definition file may be an Extensible Markup Language (XML) file. Advantageously, configuration of devices is more efficiently accomplished.

Abstract: A new master application definition is installed at a server. Responsively, the server determines the identity of a user associated with the server-side application related to the master application definition. The server may then generate an application definition file specific to the application and to the remote wireless device associated with the identified user. The application definition file may contain definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the server-side application and formatted in accordance with the definitions. The wireless device may then present a user interface for the application. Preferably, the application definition file is an XML file. Advantageously, when changes occur to previously established server-side applications, automatic updating of devices is efficiently accomplished.

Abstract: A remote wireless device registers with a server. Responsively, the server determines the identity of a server-side application associated with a user of the remote wireless device. The server may then generate an application definition file specific to the server-side application and to the remote wireless device. The application definition file may contain definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the server-side application and formatted in accordance with the definitions. The wireless device may then present a user interface for the server-side application. The application definition file may be an Extensible Markup Language (XML) file. Advantageously, configuration of devices is more efficiently accomplished.

Abstract: In a method for building distributed software, a single computer program may be written which includes distinct sets of routines defining operation at distinct computing devices (or types of computing devices) in a distributed system. Direct calls may be made between routines, even if the routines define operation of distinct computing devices. Through examination and processing of the computer program, multiple computer programs which collectively constitute distributed software for the distributed system are created. Each program defines the operation of a computing device within the system. Direct calls are emulated using instructions for inter-process communication which effect remote routine invocation transparently from the perspective of the developer. In the result, the run-time operation of each output computer program at its respective target computing device is consistent with the operation defined for that computing device within the input computer program.

Abstract: To enable use of an application on an application server at a mobile communication device, at a transaction server, a message received from the mobile is pushed out to the application. Any return messages is routed back to the mobile. The transaction server may use a queue to store all messages destined to a given application and attempt to push all messages on a given queue on receipt of a further message for the queue.

Abstract: To enable use of an application on an application server at a mobile communication device, at a transaction server, a message received from the mobile is pushed out to the application. Any return messages is routed back to the mobile. The transaction server may use a queue to store all messages destined to a given application and attempt to push all messages on a given queue on receipt of a further message for the queue.

Abstract: In a method for building distributed software, a single computer program may be written which includes distinct sets of routines defining operation at distinct computing devices (or types of computing devices) in a distributed system. Direct calls may be made between routines, even if the routines define operation of distinct computing devices. Through examination and processing of the computer program, multiple computer programs which collectively constitute distributed software for the distributed system are created. Each program defines the operation of a computing device within the system. Direct calls are emulated using instructions for inter-process communication which effect remote routine invocation transparently from the perspective of the developer. In the result, the run-time operation of each output computer program at its respective target computing device is consistent with the operation defined for that computing device within the input computer program.

Abstract: Software, methods and devices for performing a markup language based database upgrade are disclosed. One or more markup language documents contain markup language portions. Each markup language portion, which may be a hierarchy of markup language elements, describes a set of changes to be made to the database in order to effect an upgrade of the database from a starting version to a subsequent version. Based on a determined current version of a database, one of the markup language portions is selected for implementation. The set of changes to the database that is described by the selected markup language portion is implemented. Implementation may be effected through instantiation of object oriented classes corresponding to markup language elements. Selection and implementation of other markup language portions may be performed until a final database version is attained. The markup language may be Extensible Markup Language (XML).

Abstract: A remote wireless device receives a compressed message including an application definition file. The application definition file is associated with an application executing at a computing device and contains definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the application and formatted in accordance with the definitions. The wireless device may then present a user interface for the application. Preferably, the application definition file is an XML file. Similarly, application-specific network messages provided to the device are also formed using XML. Data generated by the application may be presented at the mobile device under control of a virtual machine that uses the application definition file. For efficiency, the network messages received at, and transmitted by, the wireless device may be compressed.

Abstract: Responsive to the sensing of an occurrence of an event, an action may be executed according to which a message is generated. The message may be generated with a format that is based on an application definition document. According to the application definition document, a label may be generated for associating with the message. The message and label may then be stored in a queue in a manner that allows the label to be associated with the message. Subsequent to the message having been stored, a representation of the queue may be displayed for review by a user interested in the status of the message, or the queue in general. The label associated with the message is displayed in the representation rather than the actual code of the message, thereby allowing the viewer of the display to make an informed decision regarding further activity to carried out on the message.

Abstract: A new master application definition is installed at a server. Responsively, the server determines the identity of a user associated with the server-side application related to the master application definition. The server may then generate an application definition file specific to the application and to the remote wireless device associated with the identified user. The application definition file may contain definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the server-side application and formatted in accordance with the definitions. The wireless device may then present a user interface for the application. Preferably, the application definition file is an XML file. Advantageously, when changes occur to previously established server-side applications, automatic updating of devices is efficiently accomplished.

Abstract: A remote wireless device registers with a server. Responsively, the server determines the identity of a server-side application associated with a user of the remote wireless device. The server may then generate an application definition file specific to the server-side application and to the remote wireless device. The application definition file may contain definitions for: a user interface format; a format for network messages; and a format for storing data. Using these definitions, the wireless device may receive data generated by the server-side application and formatted in accordance with the definitions. The wireless device may then present a user interface for the server-side application. The application definition file may be an Extensible Markup Language (XML) file. Advantageously, configuration of devices is more efficiently accomplished.

Abstract: To facilitate access to application data at an application server by a wireless communication device, a first markup language document describing routines for accessing the data is used to generate a second markup language document. The second document may describe invocations of the routines, data to be passed as parameters to the routines, and circumstances (e.g. arrival of messages from the wireless device) in which the invocations are to occur. The first and second documents may be stored at an intermediary transaction server along with the routines, which may be precompiled in a dynamically linked library. Object-oriented classes may be instantiated based on markup language elements in the second document and customized for performing the invocations based on attributes of the markup language elements. The creator of the second document may be different from the creator of the first document and library, and may be spared from learning application architecture details.