Abstract: Software update distribution techniques are disclosed. Authentication information is received, from a content source authenticator, by an update agent included in a client device. The authentication information comprises a list of a plurality of content sources, wherein the plurality of content sources have been verified by the content source authenticator as being authentic content sources for legitimate software applications. The update agent selects a first content source of the plurality of content sources, where the first content source is configured to provide updates for a first software application. The update agent checks the first content source for updates for the first software application.

Abstract: APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.

Abstract: Techniques for detection and installation of software on a per-user basis are disclosed. An update agent in a client device may receive configuration data for a software application, the configuration data indicating availability of updates for the software application. The client device may be configured to have user accounts for a plurality of users. The update agent may determine that the software application is a per-user application. The update agent may identify a subset of the plurality of users for whom the updates for the software application are to be installed. The update agent may download the updates for the software application, and install the updates for a first user of the subset, in response to the first user logging into the client device.

Abstract: Techniques for obtaining and providing a portion of content include receiving a request for the portion of the content, requesting and receiving one or more data chunks, processing the one or more data chunks, and providing one or more data blocks as the requested portion of the content. The processing may include validating, decrypting, and/or decompressing the one or more data chunks to create the one or more data blocks. Techniques for providing metadata and one or more data chunks may include receiving content and dividing the content into data blocks. Processing may then be performed on the data blocks to create data chunks, and the metadata may be generated from the processing. The metadata and one or more of the data chunks may be provided to a device.

Abstract: Software update distribution techniques are disclosed. Authentication information is received, from a content source authenticator, by an update agent included in a client device. The authentication information comprises a list of a plurality of content sources, wherein the plurality of content sources have been verified by the content source authenticator as being authentic content sources for legitimate software applications. The update agent selects a first content source of the plurality of content sources, where the first content source is configured to provide updates for a first software application. The update agent checks the first content source for updates for the first software application.

Abstract: APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.

Abstract: A first process executes a function in a second process. The second process may be a remote or local process. The first process may control the second process by executing a specified function in the second process. The first process may allocate space in the second process and create a stub function in the allocated space. The first process then may create a thread which runs the stub function. When the stub function is called from the first process, the stub function may call the arbitrary function, passing it the required parameters, thus enabling the first process to execute the desired function in the second process. The desired process may require any number and type of additional parameters and return any number and type of results.

Abstract: A first process executes a function in a second process. The second process may be a remote or local process. The first process may control the second process by executing a specified function in the second process. The first process may allocate space in the second process and create a stub function in the allocated space. The first process then may create a thread which runs the stub function. When the stub function is called from the first process, the stub function may call the arbitrary function, passing it the required parameters, thus enabling the first process to execute the desired function in the second process. The desired process may require any number and type of additional parameters and return any number and type of results.