Abstract: Devices, systems, and methods are provided for monitoring hydration of a user that include a fluid container including one or more sensors, e.g., pressure sensors, accelerometers, and the like, for identifying when the user consumes fluid from the container and/or determining the volume of fluid consumed. The fluid container may communicate with a mobile electronic device to monitor at least one of volume and frequency of fluid consumption and provide an output to the user related to compliance with hydration recommendations. Optionally, the system may also include a fitness tracker for monitoring one or more aspects of the user's physical activity; and the mobile device may monitor hydration of the user based at least in part on the user's physical activity.

Abstract: A data management system that protects data into a continuous object store includes a management interface having a time control. The time control allows an administrator to specify a “past” time, such as a single point or range. When the time control is set to a single point, a hierarchical display of data appears on a display exactly as the data existed in the system at that moment in the past. The time control enables the management interface to operate within a history mode in which the display provides a visual representation of a “virtual” point in time in the past during which the data management system has been operative to provide the data protection service.

Abstract: A data management system or “DMS” provides a wide range of data services to data sources associated with a set of application host servers. The data management system typically comprises one or more regions, with each region having one or more clusters. A given cluster has one or more nodes that share storage. To facilitate the data service, a host driver embedded in an application server connects an application and its data to a cluster. The host driver provides a method and apparatus for capturing real-time data transactions in the form of an event journal that is provided to the data management system. The driver functions to translate traditional file/database/block I/O into a continuous, application-aware, output data stream. Using the streams generated in this manner, the DMS offers a wide range of data services that include, by way of example only: data protection (and recovery), disaster recovery (data distribution and data replication), data copy, and data query and access.

Abstract: A data management system that protects data into a continuous object store includes a management interface having a time control. The time control allows an administrator to specify a “past” time, such as a single point or range. When the time control is set to a single point, a hierarchical display of data appears on a display exactly as the data existed in the system at that moment in the past. The time control enables the management interface to operate within a history mode in which the display provides a visual representation of a “virtual” point in time in the past during which the data management system has been operative to provide the data protection service.

Abstract: A data management system that protects data into a continuous object store includes a management interface having a time control. The time control allows an administrator to specify a “past” time, such as a single point or range. When the time control is set to a single point, a hierarchical display of data appears on a display exactly as the data existed in the system at that moment in the past. The time control enables the management interface to operate within a history mode in which the display provides a visual representation of a “virtual” point in time in the past during which the data management system has been operative to provide the data protection service.

Abstract: A machine-implemented method for building, publishing and executing interactive content applications using an XML-based language is described. In one embodiment, static content is processed or annotated to generate XML that conforms to an Interaction Markup Language (IML). IML is an XML-based language designed to represent, store, and render user interaction semantics for any printed or computer displayed content. IML is cross-platform, portable, and human readable. The IML language enables a programmer to define rich user interactions (called Interaction Objects) that include, for example, automatic user input assessment and evaluation, user feedback, hinting, adaptive behavior, and looping. IML provides for the definition of both Interaction Objects that are bound to regions on a page or computer display. Preferably, the syntax and semantics of IML allows the “meaning” of an interaction to be defined and interpreted by any runtime engine that executes IML.