Microsoft Technology Licensing, LLC

Amnon Itamar Govrin

Michael John Novak

Chris J Guzak

Scott David Hoogerwerf

Oded Yehuda Shekel

Sangeeta Ranjit

Kiernon Reiniger

Tyler Kien Beam

Relja Ivanovic

Jack Allen Nichols

Marc Wautier

Ramanarayanan Ramani

David Fields

Marcus Eduardo Markiewicz

Adam Christopher Czeisler

Jonathan Alexander Bockelman

Juan-Lee Pang

Michal Krzysztof Piaseczny

Kyle Thomas Beck

Daniel Vincent Fiordalis

Marcelo Albuquerque Fernandes Mas

Benjamin M Yim

Raghu Krishnamurhty

Subha Santhanam

Keri Talbot

Erez Kikin Gil

Yisheng Chen

Francisco Jose Garcia-Ascanio

Aleta Bashaw

David C Fields

Chris Guzak

A computing system includes at least one processor and memory storing instructions executable by the at least one processor, wherein the instructions, when executed, cause the computing system to instruct a synchronization engine to synchronize first and second versions of a file, the first version being stored on a first storage system and the second version being stored on a second storage system, receive a backoff indicator corresponding to the file, based on the backoff indicator, instruct the synchronization engine to backoff synchronizing changes to the file, and allow the changes to the file to be synchronized by a co-authoring application, maintain a first set of collaborative metadata indicative of content of the first version of the file, and maintain a second set of collaborative metadata indicative of content of the second version of the file.

Coordinating file synchronization between a sync engine and another application that supports document collaboration

Systems, components, devices, and methods for synchronizing files between a local file system and a server are provided. In an example, synchronization of individual files is paused by placing the individual files in a hold state. A non-limiting example method accesses a file stored on the local file system for synchronization with an associated file on the server and determines whether differences between the file and the associated file prevent synchronization. When determined that differences between the file and the associated file prevent synchronization, the method places the file in a hold state. The hold state pauses synchronization of the content in the file with the content of the associated file. In some examples, the method continues to synchronize topological changes to files that have been placed in the hold state and/or resumes synchronization after it is determined that the file is no longer different than the associated file.

File synchronization pausing for individual files

Disclosed are methods, systems, and machine readable mediums which provide for an automatic image scaling that may be utilized in a variety of contexts, including for scaling images inserted into documents. The image may be scaled based upon one or more scaling features that may be utilized alone or in combination. Scaling features may be described by scaling feature categories, although as will be appreciated, the scaling features may be placed in one or more categories. Example feature categories may include image characteristics; image content; content of the document and context of the image within the document; past user behavior and preferences; and the like.

Automated image scale adjustment based upon document and image context

A synchronization engine detects a notification of a change to a file. It determines whether an application associated with the file has indicated that the file is to be synchronized by the application. If so, the changes to the file are synchronized between a cloud-based storage system and a local disk by the application. Collaborative metadata, associated with the synchronized file, is updated to indicate a state of a copy of the file on the local disk and a copy of the file in the cloud-based storage system. The collaborative metadata is stored by the synchronization engine.

Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In response to a request to access content of a file system object represented by a placeholder, a client may obtain needed data from a remote storage system and stream or not stream the data to the requesting application based on whether the requesting application is capable of streaming the data.

Streaming content and placeholders

Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata, searchable text, and may also include none, some, or all of the content of the represented remote file system objects. Search data from the placeholders is integrated into a local search database of the client such that the client is able to satisfy queries and identify relevant local and remote file system objects even when the client is offline with respect to remote storage.

Searching and placeholders

Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In conjunction with local file system metadata, the placeholders allow a file system namespace to be navigated and may also allow other operations to be performed on the file system objects even when the client is offline with respect to the remote file system. After connectivity is re-established with the remote file system, the placeholders may be used in synchronizing changes.

File management with placeholders

Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In conjunction with placeholders and based on one or more factors, a client may hydrate or dehydrate file system objects of the client to follow user directives, inferred user intent, and storage policies of the client.

Hydration and dehydration with placeholders

Growing community of inventors

Issaquah, WA, United States of America

Amnon Itamar Govrin