Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Abstract: A cloud infrastructure is configured and deployed for managing services executed on a cloud platform. The cloud infrastructure includes a control datacenter configured to communicate with one or more service datacenters. The service datacenter deploys one or more application programming interfaces (API's) associated with a service. The service datacenter also deploys an administration agent. The control datacenter hosts an engine that receives requests from users to perform administration operations by invoking the administration API's. In this manner, the control datacenter functions as a centralized control mechanism that effectively distributes administration operation requests as they are received from users to service datacenters that can service the requests. The cloud infrastructure provides an auditable, compliant and secure management system for administering services for distributed systems running in the cloud.

Abstract: Disclosed are examples of systems, apparatus, methods, and computer program products for accessing and displaying shared data. In some implementations, a shared cache can be maintained. A first component and a second component can be identified. A shared record can be identified as associated with the first component and the second component. It can be determined that the shared record is valid. Shared record data from the shared record can be displayed through the first component and the second component in a user interface.

Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Abstract: A wire web component may be included in a graphical user interface (GUI) being presented on a display device. The wire web component may include one or more data fields that are each associated with a respective data value. A designated node representing the designated wire web component may be removed from a wire web component graph that includes a plurality of nodes. Each of the data fields may be associated with a respective API in the wire web component graph. A document object model (DOM) tree stored in memory may be updated to remove the designated wire web component. The GUI presented on the display device may be updated based on the updated DOM tree.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for encrypting and securely storing session data during a browser session using a session-based cryptographic key. The session data may be decrypted during the browser session or other browser sessions using the session-based cryptographic key or other backwards compatible session-based cryptographic keys. In addition, session-based cryptographic keys may be shared among browser sessions to enable encrypted session data to be decrypted across page refreshes and browser tabs.

Abstract: A wire web component graph that includes a plurality of nodes may be accessed to identify one or more application procedure interfaces (APIs) through which to update one or more data values included in a designated wire web component in a graphical user interface (GUI) being presented on a display device. Each of the data values may correspond to a respective data field represented in the wire web component graph, and each data field may be associated with a respective API in the wire web component graph. The graphical user interface may be updated based on one or more updated data values determined by communicating with the identified APIs over a network and via a communications interface.

Abstract: A wire web component graph may be constructed based on a request to provide a graphical user interface (GUI) at a client machine. The wire web component graph may include a plurality of nodes. Each of the nodes may correspond to a wire web component included in the GUI, a data value, or an application procedure interface (API). One or more API messages may be transmitted to retrieve the data values from the respective APIs based on the designated wire web component graph. A GUI including one or more of the retrieved data values may be displayed on a display device at the client machine.

Abstract: A wire web component graph may be constructed based on a request to provide a graphical user interface (GUI) at a client machine. The wire web component graph may include a plurality of nodes. Each of the nodes may correspond to a wire web component included in the GUI, a data value, or an application procedure interface (API). One or more API messages may be transmitted to retrieve the data values from the respective APIs based on the designated wire web component graph. A GUI including one or more of the retrieved data values may be displayed on a display device at the client machine.

Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph.

Abstract: A wire web component may be included in a graphical user interface (GUI) being presented on a display device. The wire web component may include one or more data fields that are each associated with a respective data value. A designated node representing the designated wire web component may be removed from a wire web component graph that includes a plurality of nodes. Each of the data fields may be associated with a respective API in the wire web component graph. A document object model (DOM) tree stored in memory may be updated to remove the designated wire web component. The GUI presented on the display device may be updated based on the updated DOM tree.

Abstract: A wire web component graph that includes a plurality of nodes may be accessed to identify one or more application procedure interfaces (APIs) through which to update one or more data values included in a designated wire web component in a graphical user interface (GUI) being presented on a display device. Each of the data values may correspond to a respective data field represented in the wire web component graph, and each data field may be associated with a respective API in the wire web component graph. The graphical user interface may be updated based on one or more updated data values determined by communicating with the identified APIs over a network and via a communications interface.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for facilitating the simulation of a variety of network conditions for the testing of network-connected applications in a hybrid application environment. A test system in communication with a web browser intercepts and overrides a network communication to the application and then substitutes an altered or degraded communication.

Abstract: A database system supports live record invalidation at one or more client systems. As client system request database resources such as data objects from the database system, the database system registers entries at an object user map that indicates which objects are active and what client systems are viewing such objects. If one of the objects is changed, the database server utilizes the object user map to identify other client systems that are viewing the changed record. The database server may transmit change event indications to the client systems, and the client systems can request the updated data corresponding to the updated object.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for encrypting and securely storing session data during a browser session using a session-based cryptographic key. The session data may be decrypted during the browser session or other browser sessions using the session-based cryptographic key or other backwards compatible session-based cryptographic keys. In addition, session-based cryptographic keys may be shared among browser sessions to enable encrypted session data to be decrypted across page refreshes and browser tabs.

Abstract: Disclosed are examples of systems, apparatus, methods, and computer program products for accessing and displaying shared data. In some implementations, a shared cache can be maintained. A first component and a second component can be identified. A shared record can be identified as associated with the first component and the second component. It can be determined that the shared record is valid. Shared record data from the shared record can be displayed through the first component and the second component in a user interface.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for encrypting and securely storing session data during a browser session using a session-based cryptographic key. The session data may be decrypted during the browser session or other browser sessions using the session-based cryptographic key or other backwards compatible session-based cryptographic keys. In addition, session-based cryptographic keys may be shared among browser sessions to enable encrypted session data to be decrypted across page refreshes and browser tabs.

Abstract: Disclosed are examples of systems, apparatus, methods, and computer program products for accessing and displaying shared data. In some implementations, a shared cache can be maintained. A first component and a second component can be identified. A shared record can be identified as associated with the first component and the second component. It can be determined that the shared record is valid. Shared record data from the shared record can be displayed through the first component and the second component in a user interface.

Abstract: Disclosed are examples of systems, apparatus, methods and computer program products for delegating handling of computing events of a mobile device application. For example, an identification of a computing event can be received. The computing event can have associated metadata. The computing event can be associated with a first component of a plurality of components of a first application executable on a mobile device. The plurality of components can comprise at least a native component and a web browser component. One or more rules can be applied to the metadata. Based on the application of the one or more rules to the metadata, a second component can be identified for handling the event. Handling of the event can be delegated to the second component.