COORDINATING CONTENT FROM MULTIPLE DATA SOURCES

• US 20110208761A1
• Filed: 02/24/2010
• Published: 08/25/2011
• Est. Priority Date: 02/24/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Zybura, John, Farmer, Ryan M.
• Application Number:
  US12/711,359
• Publication Number:
  US 20110208761A1
• Time in Patent Office: Days
• US Class Current: 707/756
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files

Abstract

Content from multiple data sources may be coordinated. A native file may be received at a first client computer from an auxiliary data store. The native file may include metadata such as a document title. The first client computer may then send a reserve title request to a primary data store. The reservation request may include the document title of the native file. The first client computer may then receive a response granting the reserve title request from the primary data store. The response may indicate that the native file is locked from further editing by another client computer. The first client computer may then convert the native file from a proprietary file format to a global file format and send the converted native file to the primary data store.

Claims

1. A computer-implemented method of coordinating content from multiple data sources, comprising:

receiving, at a first client computer, a native file from an auxiliary data store, wherein the native file comprises metadata, the metadata comprising a document title;

sending, from the first client computer, a message comprising a reserve title request to the primary data store, the reserve title request comprising the document title;

receiving, at the first client computer, a response granting the reserve title request from the primary data store, wherein upon receiving the response, the native file is locked from further editing by another client computer;

converting, at the first client computer, the native file from a proprietary file format to a global file format; and

sending, from the first client computer, the converted native file to the primary data store.

2. The method of claim 1, further comprising:

sending, from at least one other client computer, a reserve title request to the primary data store, the reserve title request comprising a document title associated with a cached version of the native file; and

receiving, at the at least one other client computer, a denial of the reserve title request from the primary data store.

3. The method of claim 2, further comprising:

receiving, at the at least one other client computer, a message from the primary data store indicating that the native file is available for editing by the at least one other client computer; and

receiving edits to the native file at the at least one other client computer to create an updated version of the native file.

4. The method of claim 3, further comprising:

sending, from the at least one other client computer, a reserve title request to the primary data store, the reserve title request comprising the document title associated with the updated version of the native file; and

receiving, at the at least one other client computer, a response granting the reserve title request from the primary data store, wherein upon receiving the response, the updated version of the native file is locked from further editing by the first client computer.

5. The method of claim 4, further comprising:

converting, at the at least one other client computer, the updated version of the native file into from a proprietary file format to a global file format;

sending, from the at least one other client computer, the converted updated version of the native file to the primary data store; and

6. The method of claim 4, further comprising receiving, at the first client computer, the updated version of the native file for viewing.

7. The method of claim 1, further comprising periodically resending, from at least one of the first client computer and the at least one other client computer, the reserve title request upon receiving a failure message from the primary data store.

8. A system for coordinating content from multiple data sources, comprising:

an auxiliary data store;

a primary data store; and

a first client computer comprising a memory for storing executable program code and a processor, wherein the processor is functionally coupled to the memory and responsive to computer-executable instructions contained in the program code, wherein the processor is operative to;

receive a native file from an auxiliary data store, wherein the native file comprises metadata, the metadata comprising a document title;

send a message comprising a reserve title request to the primary data store, the reserve title request comprising the document title;

receive a response granting the reserve title request from the primary data store, wherein upon receiving the response, the native file is locked from further editing by another client computer;

convert the native file from a proprietary file format to a global file format; and

;

send the converted native file to the primary data store.

9. The system of claim 8, further comprising a second client computer comprising a memory for storing executable program code and a processor, wherein the processor is functionally coupled to the memory and responsive to computer-executable instructions contained in the program code, wherein the processor is operative to:

send a reserve title request to the primary data store, the reserve title request comprising a document title associated with a cached version of the native file; and

receive a denial of the reserve title request from the primary data store.

10. The system of claim 9, wherein the processor of the second client computer is further operative to:

receive a message from the primary data store indicating that the native file is available for editing by the second client computer; and

receive edits to the native file at the second client computer to create an updated version of the native file.

11. The system of claim 10, wherein the processor of the second client computer is further operative to:

send a reserve title request to the primary data store, the reserve title request comprising the document title associated with the updated version of the native file; and

receive a response granting the reserve title request from the primary data store, wherein upon receiving the response, the updated version of the native file is locked from further editing by the first client computer.

12. The system of claim 11, wherein the processor of the second client computer is further operative to:

convert the updated version of the native file into from a proprietary file format to a global file format; and

send the converted updated version of the native file to the primary data store.

13. The system of claim 12, wherein the processor of the first client computer is further operative to receive the updated version of the native file for viewing.

14. The system of claim 8, wherein the processor of at least one of the first client computer and the second client computer is further operative to periodically resend the reserve title request upon receiving a failure message from the primary data store.

15. A method of coordinating content from multiple data sources, comprising:

receiving, at a first client computer, a native file from an auxiliary data store, wherein the native file comprises metadata, the metadata comprising a document title, an external identifier, and a last modification time;

sending, from the first client computer, a message comprising a reserve title request to the primary data store, the reserve title request comprising the document title, the external identifier, and the last modification time;

receiving, at the first client computer, a response granting the reserve title request from the primary data store, wherein upon receiving the response, the native file is locked from further editing by another client computer;

converting, at the first client computer, the native file from a proprietary file format to a global file format;

sending, from a second client computer, a reserve title request to the primary data store, the reserve title request comprising a document title, an external identifier, and a last modification time associated with a cached version of the native file;

receiving, at the second client computer, a denial of the reserve title request from the primary data store;

sending, from the first client computer, the converted native file to the primary data store;

receiving, at the second client computer, a message from the primary data store indicating that the native file is available for editing by the second client computer;

receiving edits to the native file at the second client computer to create an updated version of the native file;

sending, from the second client computer, a reserve title request to the primary data store, the reserve title request comprising a document title, an external identifier, and a last modification time associated with the updated version of the native file;

receiving, at the second client computer, a response granting the reserve title request from the primary data store, wherein upon receiving the response, the updated version of the native file is locked from further editing by the first client computer;

converting, at the second client computer, the updated version of the native file into from a proprietary file format to a global file format;

sending, from the second client computer, the converted updated version of the native file to the primary data store; and

receiving, at the first client computer, the updated version of the native file for viewing.

16. The method of claim 15, wherein sending, from the first client computer, a message comprising a reserve title request to the primary data store, the reserve title request comprising the document title, the external identifier, and the last modification time comprises:

determining, based at least on the document title and the last modification time, that the primary data store has a file with a document title matching the document title of the native file on the first client computer and that the native file on the first client computer is more recent than the file on the primary data store; and

sending the message comprising the reserve title request to the primary data store.

17. The method of claim 15, wherein sending, from the first client computer, a message comprising a reserve title request to the primary data store, the reserve title request comprising the document title, the external identifier, and the last modification time comprises:

determining, based at least on the external identifier and the last modification time, that the primary data store has a file with an external identifier matching the external identifier of the native file on at least one of the first client computer and the auxiliary data store and that the native file on the at least one of the first client computer and the auxiliary data store is more recent than the file on the primary data store; and

sending the message comprising the reserve title request to the primary data store.

18. The method of claim 15, wherein sending, from the first client computer, a message comprising a reserve title request to the primary data store, the reserve title request comprising the document title, the external identifier, and the last modification time comprises:

determining, based at least on the document title and the external identifier, that files in the primary data store have different document titles and different external identifiers; and

sending the message comprising the reserve title request to the primary data store.

19. The method of claim 15, wherein receiving, at the first client computer, a response granting the reserve title request from the primary data store, comprises receiving a response code and at least one of a cookie, a content identification, and an owning user identification from the primary data store, wherein the response code indicates that the native file is at least one of reserved for creation and reserved for upgrade, wherein the cookie comprises an external identifier used to correlate future messages received by the first client computer which are related to the reserve title request, wherein the content identification comprises a reference to existing content in the primary data store, and wherein the owning user identification identifies a user owning an existing lock of the native file.

20. The method of claim 15, further comprising periodically resending, from at least one of the first client computer and the second client computer, the reserve title request upon receiving a failure message from the primary data store.