Glassware 2.0 utilizes containers to enhance the efficiency of the technology. Containers allow multiple instances of the same application on our Glassware server to share the same Binaries. Libraries or Microvisor.
Within these containers we allow for access to only the necessary elements of the operating system an application requires to run. This can include applications that utilize a wide array of Windows-based operating systems, such as Windows XP, Windows 7, Windows Vista, Windows 8, etc. This approach effectively ends “end of life” for that application. It is instructive to look at an example within Windows where our technology is the first and only Windows-based application container solution.
Let’s use Windows XP components as an example; for each application that wants to share Windows XP components while keeping the other pieces separate (basically session derived), each application and each user gets their own session, and only shares the pieces that are relevant, keeping everything containerized from each other. The re-use of the one set of components or files helps increase the scalability and simplicity of the Glassware solution.
Once containerized on the server you have various choices on how you will access or connect to that application. This can be accomplished via: 1) an HTML-5 application projection, which is based upon the Glassware 2.0 Protocol technology; 2) connecting through a Java based client delivered from a browser; or 3) adding various Glassware 2.0 Microvisor components that automatically overlay additional functionality for deployment in a “native-like” state. A simple example would be accessing pinch and zoom from a tablet on an application that was not originally written to support it.
Architecturally speaking, each container has the most efficient, closest to the metal access for each application, while sharing only what is necessary.