Microsoft Technology Licensing, LLC

Glen Buhlmann

Larry Marvin Wall

Kristof Roomp

Nicholas Duncan

Viktoriya Taranov

James Squires Masson

George Perantatos

Suyog Mukund Gadgil

Gautam Vishwas Vaidya

Gunawan Herri

An optimized caching mechanism for byte range requests from a web service is provided. When a large file that is not already in cache or being transferred is requested, a background thread may be created to transfer the file and a shared data structure created to track portions of the file that are transferred. For each subsequent request for portions of the same file, the data may be sent back in chunks and the request to read each chunk from the file blocked until that chunk is filled by the background thread. Thus, the locally stored and partially filled file is shared among multiple requestors.

Optimized caching for large data requests

Non-administrators selectively move content from a source network to a destination network. The source network includes a deployment server that can deploy an item and its dependencies (if any) listed in a quick deploy list without having to get specific administrator authorization for the deployment. The deployment server can be configured to check the quick deploy list relatively frequently so that any items listed in the quick deploy list are quickly deployed. The listing of items in the quick deploy list is organized into 'jobs' and identifies a path that indicates the source and destination for each job. A job is associated with one path and specifies one or more items of the source to be deployed and a schedule to deploy the specified item(s). The deployment server is configured by the administrator with permissions for specific authors to list items in the quick deploy list.

Quick deploy of content

Data is served from a data source to a user. The data source has a plurality of pre-defined user groups. A request is received from the user for the data from the data source and a cache key corresponding to the requesting user is generated based on a set of the user groups of such user. The generated cache key represents access rights for the user based on the set of the user groups of the user. Thereafter, it is determined whether any data that satisfies the request is stored in the cache with the generated cache key.

Caching based on access rights in connection with a content management server system or the like

Data is served from a data source to a user by way of an interface having a cache. The data source has a plurality of pre-defined user groups. The interface receives a request from the user for the data from the data source and requests the data source to provide a cache key corresponding to the requesting user. The data source generates the cache key for the requesting user based on a set of the user groups of such user and returns the generated cache key to the interface. The generated cache key represents exact access rights for the user based on the set of the user groups of the user. The interface thereafter determines whether any data that satisfies the request is stored in the cache with the generated cache key.

Growing community of inventors

Kirkland, WA, United States of America

Glen Buhlmann