Techniques to share binary content

• US 8,627,411 B2
• Filed: 06/17/2010
• Issued: 01/07/2014
• Est. Priority Date: 06/17/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Li, Naizhi, Nasim, Maimoon, Vanturennout, Jeroen, Badh, Ranjib, Randhawa, Satvir, Odle, Alex, Goldberg, Matthew A, Samuel, Arimand
• Primary Examiner(s): Zand, Kambiz
• Assistant Examiner(s): Sanders, Stephen
• Application Number:
  US12/817,943
• Publication Number:
  US 20110314516A1
• Time in Patent Office: 1,300 Days
• Field of Search: 726/3
• US Class Current: 726/3
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06F 9/522 Barrier synchronisation

Abstract

Techniques to share binary content are described. An apparatus may comprise a first related client having a message platform with a file share feature and an object store, the file share feature operative to retrieve a data object for a publishing client having a defined relationship with the first related client and a second related client, the first related client to send the data object to the second related client on behalf of the publishing client, and the object store operative to store and manage the data object using a unique name identifier received with the data object. Other embodiments are described and claimed.

Claims

1. A computer-implemented method, comprising:

authenticating that a first related client has a dyadic relationship with a publishing client, wherein the first related client is a separate device from the publishing client;

receiving a data object from the publishing client at the first related client based on the authentication of the dyadic relationship with the publishing client, wherein the data object is also stored to an online storage of a web service by the publishing client;

storing the data object of the publishing client at the first related client;

receiving a request at the first related client for the data object from a second related client having a dyadic relationship with the publishing client, wherein the second related client is a separate device from the publishing client and from the first related client; and

sending the data object from the first related client to the second related client.

2. The computer-implemented method of claim 1, comprising storing the data object at the first related client using a unique object name received with the data object.

3. The computer-implemented method of claim 1, comprising receiving the data object for the publishing client by the first related client over a direct or indirect connection between the publishing client and the first related client.

4. The computer-implemented method of claim 1, comprising receiving the data object for the publishing client by the first related client from a network storage server.

5. The computer-implemented method of claim 1, wherein authenticating that the first related client has a dyadic relationship with the publishing client comprises authenticating that the first related client has a social-networking relationship with the publishing client in a social-networking system.

6. The computer-implemented method of claim 1, comprising authenticating that the second related client has a dyadic relationship with the publishing client.

7. The computer-implemented method of claim 1, comprising querying a server to authenticate that the second related client has a dyadic relationship with the publishing client.

8. The computer-implemented method of claim 1, comprising receiving security information by the first related client to authenticate that the second related client has a dyadic relationship with the publishing client.

9. The computer-implemented method of claim 1, comprising authenticating that the first related client has a defined relationship with the second related client.

10. The computer-implemented method of claim 1, comprising sending the data object from the first related client to the second related client over a direct or indirect connection.

11. An article comprising a storage device containing instructions that when executed enable a system to:

authenticate that a second related client has a dyadic relationship with a publishing client, wherein the second related client is a separate device from the publishing client;

receive a unique object name for a data object of the publishing client, the data object stored at a first related client, at the second related client based on the authentication of the dyadic relationship with the publishing client, the first related client having a dyadic relationship with the publishing client, wherein the data object is also stored to an online storage of a web service by the publishing client, wherein the first related client is a separate device from the publishing client and from the second related client;

send a request from the second related client to retrieve the data object associated with the unique object name to the first related client; and

receive the data object from the first related client at the second related client.

12. The article of claim 11, further comprising instructions that when executed enable the system to send security information to the first related client to authenticate that the second related client has a defined relationship with the publishing client.

13. The article of claim 11, further comprising instructions that when executed enable the system to receive a distribution list indicating that the data object is stored by one or more related clients including the first related client.

14. The article of claim 11, further comprising instructions that when executed enable the system to generate a distribution list indicating that the data object may be stored by one or more related clients including the first related client.

15. The article of claim 11, further comprising instructions that when executed enable the system to select the first related client from a distribution list using one or more distribution rules.

16. An apparatus, comprising:

a first related client having a message platform with a file share feature and an object store, the file share feature operative to authenticate that the first related client has a dyadic relationship with a publishing client, retrieve a data object for the publishing client based on the authentication of the dyadic relationship with the publishing client, wherein the first related client is a separate device from the publishing client, wherein the data object is also stored to an online storage of a web service by the publishing client, the publishing client having a dyadic relationship with a second related client, wherein the second related client is a separate device from the publishing client and from the first related client, the first related client to send the data object to the second related client on behalf of the publishing client, and the object store operative to store and manage the data object using a unique name identifier received with the data object.

17. The apparatus of claim 16, the file share feature operative to authenticate that the second related client has a defined relationship with the publishing client.

18. The apparatus of claim 16, the file share feature operative to authenticate that the second related client has a defined relationship with the first related client.

19. The apparatus of claim 16, comprising a file system operative to store the data object using the unique name identifier.

20. The apparatus of claim 16, comprising a cache operative to store the data object using the unique name identifier.