Abstract: Example apparatus and methods detect a query to a partition in a table store that is arranged in a table-entity-property organization. A partition is a collection of entities having the same partition key value. If the query seeks to filter on a specific entity in the partition, then the partition may be copied to a memory (e.g., structured shared cache, shared memory) that is prepared with one or more indexes that facilitate filtering the partition. Example apparatus and methods may copy the partition from the table store into the memory and then filter the partition on the specific field from the memory using the one or more indexes. Filtering the partition on the specific field may proceed in parallel, perhaps massively in parallel, using all the indexes available for the memory.

Abstract: Various embodiments relating to synchronizing changes to a shared list of items between different devices are provided. In one embodiment, a first set of change operations for a first version of a shared list may be received from a first device. The first set of change operations may be performed on the first version of the shared list to produce a second version of the shared list. A second set of change operations for the first version of the shared list may be received from a second device. The second set of change operations may be performed on the second version of the shared list to produce a third version of the shared list that maintains changes that are made by the first set of change operations but that are not made by the second set of change operations.

Abstract: Example apparatus and methods detect a query to a partition in a table store that is arranged in a table-entity-property organization. A partition is a collection of entities having the same partition key value. If the query seeks to filter on a specific entity in the partition, then the partition may be copied to a memory (e.g., structured shared cache, shared memory) that is prepared with one or more indexes that facilitate filtering the partition. Example apparatus and methods may copy the partition from the table store into the memory and then filter the partition on the specific field from the memory using the one or more indexes. Filtering the partition on the specific field may proceed in parallel, perhaps massively in parallel, using all the indexes available for the memory.

Abstract: Techniques and a graphical user interface for abstracting a request from a development environment to an object model of an object store are disclosed herein. A request for data is made by the development environment, and the request is abstracted to make in compatible with the object model (e.g., by negating properties related to bitness, versioning, etc.). The request is transmitted to a broker process that retrieves a method and/or data commands corresponding to the request. The broker process may also decode one or more method parameters of the request. If one or more method parameters are not compatible with the object model, an adapter may be loaded into the object model to make the object model compatible with the request. The broker process may also transmit the method, data commands, and/or request to the object model wherein the request is fulfilled by the object model.

Abstract: Techniques and a graphical user interface for abstracting a request from a development environment to an object model of an object store are disclosed herein. A request for data is made by the development environment, and the request is abstracted to make in compatible with the object model (e.g., by negating properties related to bitness, versioning, etc.). The request is transmitted to a broker process that retrieves a method and/or data commands corresponding to the request. The broker process may also decode one or more method parameters of the request. If one or more method parameters are not compatible with the object model, an adapter may be loaded into the object model to make the object model compatible with the request. The broker process may also transmit the method, data commands, and/or request to the object model wherein the request is fulfilled by the object model.

Abstract: Various embodiments relating to managing media content availability in a playlist are provided. In one embodiment a playlist including a plurality of media content items may be received. Media content items included in the playlist that are not accessible due to a lack of access rights may be identified as inaccessible media content items. For each inaccessible media content item, if a different version of that inaccessible media content item is available as an accessible media content item, that inaccessible media content item may be replaced with the accessible media content item in the playlist.

Abstract: Various embodiments relating to synchronizing changes to a shared list of items between different devices are provided. In one embodiment, a first set of change operations for a first version of a shared list may be received from a first device. The first set of change operations may be performed on the first version of the shared list to produce a second version of the shared list. A second set of change operations for the first version of the shared list may be received from a second device. The second set of change operations may be performed on the second version of the shared list to produce a third version of the shared list that maintains changes that are made by the first set of change operations but that are not made by the second set of change operations.

Abstract: Techniques and a graphical user interface for abstracting a request from a development environment to an object model of an object store are disclosed herein. A request for data is made by the development environment, and the request is abstracted to make in compatible with the object model (e.g., by negating properties related to bitness, versioning, etc.). The request is transmitted to a broker process that retrieves a method and/or data commands corresponding to the request. The broker process may also decode one or more method parameters of the request. If one or more method parameters are not compatible with the object model, an adapter may be loaded into the object model to make the object model compatible with the request. The broker process may also transmit the method, data commands, and/or request to the object model wherein the request is fulfilled by the object model.