Microsoft Technology Licensing, LLC

Ivaylo G Dimitrov

John David Rodrigues

Kristof Roomp

Gruia Pitigoi-Aron

Cheng Ho

Lincoln Liu

Alok Dhariwal

Brandon Pai

Kumar Pasumarthy

Yurong Jiang

Si Lao

Davi Einstein Melges Arnaut

Sining Ma

Systems and techniques for a large scale online lossless animated GIF processor are described herein. In an example, a lossless animated GIF processor is adapted to receive an animated GIF image and decode a first and second frame of the animated GIF image, wherein the decoding identifies a disposal method for each frame. The lossless animated GIF processor may determine an optimized disposal method for the second frame based on transparency pixels in the second frame and an overlap estimation between the second frame and the first frame. The lossless animated GIF processor may encode the second frame with the optimized disposal method. The lossless animated GIF processor may be further adapted to identify pixels in an area of interest, designate pixels outside the area of interest as transparent, and encode the area of interest and the pixels designated as transparent for the second frame.

Large scale online lossless animated GIF processor

Systems and techniques of de-duplicating file and/or blobs within a file system are presented. In one embodiment, an email system is disclosed wherein the email system receives email messages comprising a set of associated attachments. The system determines whether the associated attachments have been previously stored in the email system, the state of the stored attachment, and if the state of the attachment is appropriate for sharing copies of the attachment, then providing a reference to the attachment upon a request to share the attachment. In another embodiment, the system may detect whether stored attachments are corrupted and, if so, attempt to repair the attachment, and possibly, prior to sharing references to the attachment.

De-duplicating attachments on message delivery and automated repair of attachments

A system, method, and apparatus are provided for limiting or preventing write amplification. Full documents (which may be stored as blobs) are stored as monolithic entities in that only the entire documents can be written or read. When one or more fields or other portions of a document are determined to be 'hot,' those fields are stored in a separate structure, possibly adjacent to the document. When only these fields are updated, the document need not be rewritten. For read requests, both structures are read and merged to yield a true version of the document. Fields may be considered hot based on criteria such as frequency of access, ratio of the fields' size to the size of the document, type of document, the application associated with the document, etc.

Preventing write amplification during frequent data updates

Growing community of inventors

Mountain View, CA, United States of America

Ivaylo G Dimitrov