Arnab Bose

A process to take a collaborative file and publish a version of it into a content repository for broader sharing across a company, or public access.

Strategy for efficient and user friendly versioning of Files

Embodiments described herein may involve enabling applications to cooperate with a system-level sync framework. The sync framework may provide system synchronization of files between user devices and a cloud storage service. Arbitrary applications on a user computing device can communicate with the sync framework to temporarily suspend synchronization of a specified file by the sync framework. The application can register functions with the sync framework that the sync framework can invoke in… Mehr zeigen

Embodiments described herein may involve enabling applications to cooperate with a system-level sync framework. The sync framework may provide system synchronization of files between user devices and a cloud storage service. Arbitrary applications on a user computing device can communicate with the sync framework to temporarily suspend synchronization of a specified file by the sync framework. The application can register functions with the sync framework that the sync framework can invoke in relation to suspending synchronization, continuing to provide system-level access to the file for arbitrary applications, and resuming synchronization. Weniger anzeigen

Logic to ensure that a set of deltas submitted to a server are grouped into a target blob size that matches what the server is designed to handle at low cost with low churn.

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… Mehr zeigen

Logic to ensure that a set of deltas submitted to a server are grouped into a target blob size that matches what the server is designed to handle at low cost with low churn.

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. Weniger anzeigen

In order to synchronize file deltas efficiently over the wire lots of GUIDs are used to define the graph. This is a strategy that helps reduce the amount of bytes used up by the IDs and reduce memory consumption and IO.

This is a system that allows clients to receive hashes for updates instead of the actual data and then fetch those hashes from peers on the local network or a previously seeded local caching server.

Concepts and technologies are described herein for cache management. In accordance with the concepts and technologies disclosed herein, the server computer can be configured to communicate with a client device configured to execute a cache module to maintain a cache storing data downloaded… Mehr zeigen

This is a system that allows clients to receive hashes for updates instead of the actual data and then fetch those hashes from peers on the local network or a previously seeded local caching server.

Concepts and technologies are described herein for cache management. In accordance with the concepts and technologies disclosed herein, the server computer can be configured to communicate with a client device configured to execute a cache module to maintain a cache storing data downloaded from and/or uploaded to the server computer by the client device. The server computer can be configured to receive requests for data stored at the server computer. The server computer can be configured to respond to the request with hashes that correspond to the requested data. The client device can search the cache for the hashes, obtain the data from the cache if the hashes are found, and/or download the data from the server computer if the hashes are not found. The client device also can be configured to update the cache upon uploading the data to the server computer. Weniger anzeigen

Typically server file locks take an exclusive lock on the document and prevent access from other applications. This patent covers a strategy to allow the server to mimic this behavior during a document coauthoring session and prevent access from end points which don't understand the rules of coauthoring while allowing end points which do (and support merging content, et al) to essentially ignore the file lock and update the document.

When a document is opened from a remote web server, the remote web server may expose many web service end points. Over time as features are authored in the client applications to utilize these end points, different platform networking APIs are used. This is a strategy to ensure that in this scenario, the end user has to only authenticate against the web server once (if credentials are not saved) even if multiple network requests are being made over multiple platform networking APIs to multiple… Mehr zeigen

When a document is opened from a remote web server, the remote web server may expose many web service end points. Over time as features are authored in the client applications to utilize these end points, different platform networking APIs are used. This is a strategy to ensure that in this scenario, the end user has to only authenticate against the web server once (if credentials are not saved) even if multiple network requests are being made over multiple platform networking APIs to multiple web service end points on the same web server. Weniger anzeigen

Process for detecting server availability from rich internet enabled productivity applications to ensure that user experiences remain responsive in the face of loss of connectivity but can still take full advantage of server based content and functionality when available.

This patent describes a strategy of reducing server load and improving reliability in the face of synchronizing rapid changes made to documents during multi-user editing sessions. This was used by SharePoint 2010 to deliver on coauthoring scenarios for Word, OneNote and PowerPoint while also enabling key enterprise focused features like document metadata search, required metadata enforcement, document workflows, etc.

This is a patent for the Office Document Cache which first shipped in Office 2010. This enabled Office applications to deliver on file open and save experiences against remote web servers and cloud services that were network state agnostic - to the end user file save was as fast as local disk, and uploads/sync happened in the background but typical online collaboration features such as file locks were still preserved.

This patent covers another key aspect of enabling multi-user authoring in Office applications - the ability to synchronize user presence and other associated metadata related to the editing session (which are related to but not necessarily contained within the document being authored) at different frequencies and with high efficiency.

This is a patent for the MS-FSSHTTP incremental document synchronization protocol which enables fast, delta sync of documents against the cloud and is also the foundation for coauthoring in Office applications like Word, PowerPoint, OneNote and Visio.

This patent covers the strategy used to enable simultaneous multi-user editing in Word, PowerPoint and Visio. For the Office 2010 release my team invented this method of accessing and updating server based Office documents in a manner which allowed users from rich, desktop client applications to edit the same file in an intuitive and simple manner (presence of other authors, automatic 3-way merging of changes, notification when changes were available, etc).

Share business objects like Accounts, Opportunities and Contacts via a feed based collaborative system while maintaining ACL privileges.