Abstract: In some implementations, a computing device can proactively determine a destination and request traffic information for routes from a starting location to the destination. In some implementations, a computing device can identify some routes between a starting location and a destination as non-recommended routes and recommend other routes. In some implementations, a computing device can rank routes between a starting location and a destination based on automatically-determined user interest. In some implementations, a computing device can determine a user is familiar with a route and adjust the information presented to the user about the route accordingly.

Abstract: The BIN ENABLED DATA OBJECT ENCRYPTION AND STORAGE APPARATUSES, METHODS AND SYSTEMS (“MBIN”) transforms bin creation requests, bin templates and unencrypted object storage inputs, using MBIN components, into encrypted object storage bins and encrypted bin objects. A method comprises the creation of encrypted object storage bins, the storage of encrypted bin objects, and an application framework that allows privileged applications to leverage the capabilities of and data stored in the encrypted object storage bins.

Abstract: One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.

Abstract: The BIN ENABLED DATA OBJECT ENCRYPTION AND STORAGE APPARATUSES, METHODS AND SYSTEMS (“MBIN”) transforms bin creation requests, bin templates and unencrypted object storage inputs, using MBIN components, into encrypted object storage bins and encrypted bin objects. A method comprises the creation of encrypted object storage bins, the storage of encrypted bin objects, and an application framework that allows privileged applications to leverage the capabilities of and data stored in the encrypted object storage bins.

Abstract: The techniques disclosed herein facilitate online audience targeting based on brand and product interest/enthusiasm as determined by a measurement metric that is a function of one of more (and preferably all) of the following: recency data, frequency data, intensity data, consumption data, site data, meta data related to given videos, data, and other demographic data.

Abstract: The BIN ENABLED DATA OBJECT ENCRYPTION AND STORAGE APPARATUSES, METHODS AND SYSTEMS (“MBIN”) transforms bin creation requests, bin templates and unencrypted object storage inputs, using MBIN components, into encrypted object storage bins and encrypted bin objects. A method comprises the creation of encrypted object storage bins, the storage of encrypted bin objects, and an application framework that allows privileged applications to leverage the capabilities of and data stored in the encrypted object storage bins.

Abstract: The techniques disclosed herein facilitate online audience targeting based on brand and product interest/enthusiasm as determined by a measurement metric that is a function of one of more (and preferably all) of the following: recency data, frequency data, intensity data, consumption data, site data, meta data related to given videos, data, and other demographic data.

Abstract: The BIN ENABLED DATA OBJECT ENCRYPTION AND STORAGE APPARATUSES, METHODS AND SYSTEMS (“MBIN”) transforms bin creation requests, bin templates and unencrypted object storage inputs, using MBIN components, into encrypted object storage bins and encrypted bin objects. A method comprises the creation of encrypted object storage bins, the storage of encrypted bin objects, and an application framework that allows privileged applications to leverage the capabilities of and data stored in the encrypted object storage bins.

Abstract: This disclosure describes methods and systems to quantify and understand the behavior and consumption patterns of audiences with respect to Internet video and rich media applications. In operation, an end user video player or a rich media application (such as an interactive advertisement built with Flash or other method) is instrumented to capture data. The data is collected by a service provider and made available for viewing by customers of a video experience and rich media behavior measurement service.

Abstract: This disclosure describes methods and systems to quantify and understand the behavior and consumption patterns of audiences with respect to Internet video and rich media applications. In operation, an end user video player or a rich media application (such as an interactive advertisement built with Flash or other method) is instrumented to capture data. The data is collected by a service provider and made available for viewing by customers of a video experience and rich media behavior measurement service.

Abstract: One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated. If the application is able to write to a local file system, usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server. The usage information tracked comprises “features,” “faults” and “failures” of the application, independent of platform, location, and number of deployed application instances.

Abstract: One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated. If the application is able to write to a local file system, usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server. The usage information tracked comprises “features,” “faults” and “failures” of the application, independent of platform, location, and number of deployed application instances.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. Preferably, an application under test is one of: application software, a script-enabled web application, or a rich Internet application (RIA). During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated, typically in one of two ways. If the application is able to write to a local file system (in the user's machine), usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. Preferably, an application under test is one of: application software, a script-enabled web application, or a rich Internet application (RIA). During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated, typically in one of two ways. If the application is able to write to a local file system (in the user's machine), usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server.

Abstract: A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. Preferably, an application under test is one of: application software, a script-enabled web application, or a rich Internet application (RIA). During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated, typically in one of two ways. If the application is able to write to a local file system (in the user's machine), usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine's local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server.

Abstract: One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.