Abstract: Embodiments can enable the uploading of a newer version of a plugin package to a plugin service without affecting an existing user session that is using an older version of the plugin package. When a new user session begins, the plugin service can monitor one or more plugin packages and the versions used during the new user session. Throughout the user session, the plugin service continues to make the plugin packages available to the user regardless of newer versions being uploaded to the plugin service. In the meantime, multiple clients with different user sessions may be using different and possibly newer versions of the plugin packages at the same time. The plugin service can remove an older version of a plugin package when it determines that there are no longer any active user sessions utilizing the older version of the plugin package.

Abstract: Embodiments can provide interactivity to one or more components (e.g., windows, dialog boxes, tool bar, etc.) in a visual analyzer application while blocking interactivity for other components displayed on a GUI of the application. A contribution mechanism can be leveraged where a broadcast message can be sent to various components displayed on the GUI of the application. The various components within the application can then indicate whether they would like to be kept interactive during a triggering event (e.g., upon selection of a certain component). Upon receiving the indication that the components would like to remain interactive, the application allows those components to remain interactive while preventing access to other components in the GUI.

Abstract: Embodiments are directed to utilizing reverse dependency injection for managing bootstrapping of applications in web browser and mobile environments. By using reverse dependency injection, embodiments enable a component to declare that it is a “dependency of” another component in a visual analyzer application. This ensures that the dependencies are loaded before the other component is loaded, thereby minimizing delays when a user starts up an application. In some embodiments, information identifying a plugin to be loaded can be received. Embodiments can determine configuration information for the plugin where the configuration information includes both forward and reverse dependencies. Embodiments may generate, based on the configuration information, a data structure that represents the forward and reverse dependencies. Embodiments may analyze the data structure to determine an ordered list of loadings.

Abstract: Mechanisms can be provided for locking a component and extending the lock to one or more additional component(s) in a visual analyzer application. Embodiments can receive a request for a first component of a document for a first thread where the document is displayed by a graphical user interface (GUI) and has components including the first component and a second component. A lock manager may lock the first component. An action handler can determine, based on code associated with an event pertaining to the request, that the second component also needs to be locked. The lock manager may lock the second component for a same thread, if the first and second components are not currently locked. Additional user actions directed to other components of the application not currently locked may still proceed, permitting asynchronous calls to be processed without interference with a previous action that has already started.