Microsoft Technology Licensing, LLC

Andrew Sean Watson

Simon Clarke

Simon Skaria

Mitesh Patel

Miko Arnab Sakhya Singha Bose

Steven James Rayson

Humberto Lezama Guadarrama

Naresh Kannan

Goksel Genc

Gary Chang

Jonathan Bailor

Mark Rolland Knight

Christopher James Antos

Andrew Grey Carlson

David Charles Oliver

Ming-wei Wang

Elena Petrova

Don Adam Hedgpeth

Ahmed Hassan Mohamed

Hai Liu

Sean Erik McAteer

Andrew Keith Glover

Meir Elie Abergel

Jose Araujo Barreto

Frederico A Mameri

Ronakkumar N Desai

Mark John Walker

Clement Basile Fauchere

Steve Rayson

Elisabeth Olson

Sundar Subbarayan

Jay Paulus

Robert G Lefferts

George N Armah

Miko Arnab Sakya Singha Bose

Jiashan Song

Shaun W Kimber

Yigithan Dedeoglu

Dustin G Fresenhahn

Dave M Kruse

V R Kishore Chintalapati

Meir E Abergel

George Armah

Andrew Glover

The concepts relate to data handling, and more specifically to data handling scenarios where data is revised on one computer and stored on another computer. One example can obtain a set of blobs relating to revisions of a file. The example can determine a target size of datastore blobs. In an instance where a total size of the set of blobs is less than the target size, this example can aggregate the set of blobs into an individual datastore blob. Otherwise, the example can identify new or edited individual blobs of the set and aggregate the new or edited individual blobs into first datastore blobs. The example can also aggregate other individual blobs of the set into second datastore blobs.

Data handling

Systems and methods for restoring a file system to a point-in-time without relying on a backup. One system includes an electronic processor configured to automatically restore a file system to a specified point-in-time by (a) automatically restoring, from a recycle bin, items deleted from the file system after the point-in-time, (b) automatically deleting, from the file system, items created within the file system after the point-in-time, (c) automatically moving items moved within the file system after the point-in-time to a location within the file system associated with the point-in-time, (d) automatically deleting, from the file system, items copied within the file system after the point-in-time, (e) automatically renaming items renamed within the file system after the point-in-time to a name associated with the point-in-time, and (f) automatically restoring, from a version history, a version associated with the point-in-time for items with content modified after the point-in-time.

File system point-in-time restore using recycle bin and version history

Techniques for limiting synchronization conflicts during file synchronization in a computing system are described herein. In one embodiment, a method includes detecting a change to a local copy a computer file on a client device. The local copy is associated with a local token. The method also includes obtaining a server token associated with a server copy of the same computer file on a file server and determining whether the local token matches the server token. If the local and server tokens match each other, the method includes uploading the local copy to the file server to overwrite the server copy even though the server copy contains a change to the computer file that is different than a change to the local copy of the same computer file.

File synchronization with reduced conflicts in computing systems

A method for scaling out database information may include creating second database instantiation. The method may include configuring one or more partitions of a first database for transfer to the second database and configuring the second database for receiving the one or more first database partitions. The method may also include transferring the one or more first database partitions to the second database.

Database scale-out

Example systems and methods are directed at maintaining and retrieving presence metadata. One example method includes receiving a request from a first client to edit a document file, and sending short-term check out metadata to the first client to begin an editing session. The method also includes writing the transition ID to a transition table stored in a cache, wherein the presence of another transition ID in the cache indicates that a document has switched from a single-client mode to a multi-client mode. An example system includes a processing unit operative to receive a document, the document including short-term check out metadata indicating an editing session has begun, ping a cache to determine if another transition ID is stored in the cache, and send a transition ID to a transition table stored in a cache to switch from a single-client mode to a multi-client mode.

Caching infrastructure

Enhanced browser caching is provided through a file identifier attribute employed at a front end server level for deterministic marking A front end server may use an attribute of a file identifier such as an attached parameter, a pattern, a directory associated with the file, or similar attributes to change the links it emits into other content in order to prompt the browsers to request new files. The attribute may be changed (e.g. incremented) based on a web change associated with the content being served.

Optimizing browser caching through deterministic marking of files

Distributed storage of collaboration data is managed over internal and external data stores in a collaboration service environment based on categorization of the data. The categorization may be based on type of data (e.g. structured vs. unstructured), how the data is accessed, an expected storage life for the data, back-up requirements, and the like. Data that can be stored externally according to its category is then directed to the external storage through a storage provider. A unique identifier associated with the location of the externally stored data is saved in one of the internal data stores for seamless retrieval of data in a transparent manner to the user.

Distributed storage for collaboration servers

Examples are related to systems and methods for controlling access to document files on a document server. One example system includes document files stored on a document server, at least one of the document files referencing a file lock, and a document access processing module. The example document access processing module includes a file sharing processing module that determines a coauthoring status of a software application of a client computer requesting access to the document file, and a file lock processing module that stores one or more file locks and that controls the setting and resetting of file locks. The example document access processing module uses the coauthoring status of the software application and the file lock status of a document file to determine whether a software application is permitted to have write access to the document file.

Controlling access to documents using file locks

A storage system according to one embodiment for managing a first file includes a blob storage and a handler. The blob storage may be configured to store data related to the first file temporarily. The handler may be configured to store in the blob storage any data related to the first file and received from an application. The handler also may be configured to transfer at least a portion of the data from the blob storage to persistent storage in response to a commit instruction received from an application or generated by the handler. The handler also may be configured to retrieve any portion of the data stored in the blob storage and to send the same to a requesting application in response to an access request.

Data storage for file updates

A dynamically configurable list management system that supports list elements of multiple content types is presented. Each list element is associated with an element type via an element type identifier. The element type identifier uniquely identifies the element type to the list management system. Each property associated with each element type is included in the list. Each property is identified by a unique property identifier. When adding a list element of a new element type to an existing list that does not include any elements of the new element type, the list management system identifies every property associated with the new element type. For each property associated with the new element type, the list management system determines which properties are not already included in the list, and adds those properties that are not already including to the list.

Dynamically configurable lists for including multiple content types

Conventions for extending compounded web authoring methods to a web authoring protocol such as WebDAV. More particularly, a request can be provided with special header information to signify a method compounded with a method indicated by a verb in the request. Techniques for clients and servers to use the web authoring extensions. Extended error handling to allow servers to provider richer web authoring error information to clients.

Compounding of HTTP authoring protocol

Growing community of inventors

Redmond, WA, United States of America

Andrew Sean Watson