The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jun. 19, 2012
Filed:
Nov. 17, 2008
Jin Wang, Kirkland, WA (US);
Luming Wang, Bellevue, WA (US);
Malik Hussain, Woodinville, WA (US);
Zaiwei Du, Bellevue, WA (US);
Zhenyu Tang, Sammamish, WA (US);
Patrick J. Baumgartner, Kirkland, WA (US);
Mark Xiaohong Yang, Sammamish, WA (US);
Peter Eberhardy, Seattle, WA (US);
Jin Wang, Kirkland, WA (US);
Luming Wang, Bellevue, WA (US);
Malik Hussain, Woodinville, WA (US);
Zaiwei Du, Bellevue, WA (US);
Zhenyu Tang, Sammamish, WA (US);
Patrick J. Baumgartner, Kirkland, WA (US);
Mark Xiaohong Yang, Sammamish, WA (US);
Peter Eberhardy, Seattle, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
Data processing architecture where submitters can write data and/or metadata changes to a destination through an asynchronous interface. The architecture includes a ticketing system that issues a ticket (a unique identifier) to the submitter in response to receiving a changelist from the submitter. When the changes are successfully completed at the destination, the cached destination data can be re-downloaded to the submitter, and the changes cached in the submitter, discarded. Absent this capability, a user has to manually manage the cached changes and cached data. The architecture can be distributed in that multiple submitters can submit changelists. The destination provides data integrity by managing submissions to assist in ensuring data integrity across multiple submissions. Automatic changelist cleanup is provided on the submitter so that changelists do not impact performance, memory, and storage.