Abstract: Disclosed is a computerized system for error handling of applications executing on a device. The disclosed systems and method involve connecting over a network with a user device that executes an application, where the application is compiled with compilation instructions associated with the user device and a meta-data signature of the user device. The application is executed, and a message is received. If the message indicates an error has occurred, it is parsed. If the message indicates a state of the application, is its also parsed. The disclosed systems and methods then create, based on the parsing of the received message, adapted compilation instructions corresponding with the user device and the meta-data signature. A device database is then updated accordingly.

Abstract: A method of configuring an email client is disclosed. An email address is received. The email address is parsed to obtain a domain. A mailserver configuration is generated based on the domain. The email client is configured according to the mailserver configuration.

Abstract: A method of configuring an email client is disclosed. An email address is received. The email address is parsed to obtain a domain. A mailserver configuration is generated based on the domain. The email client is configured according to the mailserver configuration.

Abstract: A method of delivering a user specific customized service to a mobile user device is disclosed. User specific customized service information is received over a first channel. An identifier for the user specific customized service is generated. A link is sent that includes the identifier of the user specific customized service over a second channel. The user specific customized service identifier is received. The user specific customized service over a third channel is sent.

Abstract: A method of delivering a user specific customized service to a mobile user device is disclosed. A user identifier is provided to an individual user associated with a device. Upon requesting a device configuration for the device, metadata pertaining to the device configuration is received from the device. A device signature is then created by parsing the received metadata and the device configuration is identified based on the device signature. A set of components customized for the device configuration is selected based on the device signature and a template having a set of predetermined components. The selection includes mapping the device signature to the template. The selected set of components is then compiled into a customized instance of the application for the device. Access to the instance of the application is provided to the user via a customized pointer.

Abstract: A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.

Abstract: A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.

Abstract: A method of delivering a user specific customized service to a mobile user device is disclosed. User specific customized service information is received over a first channel. An identifier for the user specific customized service is generated. A link is sent that includes the identifier of the user specific customized service over a second channel. The user specific customized service identifier is received. The user specific customized service over a third channel is sent.

Abstract: Data relating to execution flows at a computer system is compressed and aggregated across multiple execution flows by categorizing each execution flow into an execution flow shape. The execution flows may represent sequences of software components that are invoked. The execution flow shapes are developed by observing the execution flows at the computer system and applying lossy compression rules, such as representing multiple iterations of a loop as a single iteration, skipping certain types of software components, such as those having a specified call stack depth, treating some of the software components as being optional, and ignoring recursive calls by the software components. The aggregation and compression allow the information from all execution flows to be combined into a small enough data set that can be reported without consuming unduly large processing overhead while still preserving as many of the interesting aspects of the execution flows as possible.

Abstract: Data relating to execution flows running on different processes or threads at a computer system is correlated. The execution flows may represent sequences of software components that are invoked or other computer system resources that are consumed. A first execution flow fulfills a first request by transmitting a second request which initiates a second execution flow, such as at another computer system. The second request includes meta data which identifies a context of the first request, such as a URL, an agent which monitors the first execution flow, and the component in the first execution flow which initiated the second request. A manager receives information regarding the first execution flow from the first agent, and information regarding the second execution flow, along with the meta data, from a second agent, for correlating the first and second execution flows. The received information may include execution flow shape data.

Abstract: Data relating to execution flows at a computer system is aggregated across multiple execution flows by categorizing each execution flow into an execution flow shape. The execution flows may represent sequences of software components that are invoked or other computer system resources that are consumed. The execution flow shapes are developed by observing and recording the execution flows at the computer system and applying lossy compression rules. Execution flows are categorized into an execution flow shape which is a closest match. The execution flow data may be aggregated by an agent at the computer system, and communicated to a manager for subsequent use. The aggregation combines the information from all execution flows into a small enough data set that can be reported without consuming unduly large processing overhead while still preserving as many of the interesting aspects of the execution flows as possible.