File sharing via link generation

• US 10,212,211 B2
• Filed: 07/17/2017
• Issued: 02/19/2019
• Est. Priority Date: 06/22/2011
• Status: Active Grant

• Current Assignee: Dropbox, Inc.
• Original Assignee: Dropbox, Inc.
• Inventors: Ferdowsi, Arash, Houston, Drew, Ying, Jonathan, Bartelma, Jeffrey
• Primary Examiner(s): Walsh, John B
• Application Number:
  US15/651,741
• Publication Number:
  US 20180048698A1
• Time in Patent Office: 582 Days
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 3/0622 in relation to access
• CPC Class Codes: G06F 3/0661 Format or protocol conversion arrangements
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

Users specify that a file set comprising their files, folders, or other content owned by the users should be made accessible via a link, such as a uniform resource locator (URL). The system which stores and provides access to the files accordingly creates a link that specifies the file set to be made accessible. The users may distribute the link to recipients with whom the file set is to be shared, and the distribution may be performed in any manner that the users choose.

Claims

1. A computer-implemented method executed by a file access server, comprising:

receiving, from a first client device, a request for a first link to a server file, the request received in response to a user of the first client device selecting a user interface element, the server file stored on the file access server;

responsive to receiving the request, generating the first link specifying the server file;

receiving, from a second client device different from the first client device, a first access request via the first link; and

responsive to receiving the first access request, providing a first preview representation of the server file to the second client device;

receiving a request to synchronize with the file access server, the request including a modified copy of the server file having content or metadata that is different from that of the server file stored on the file access server;

replacing the server file on the file access server with the modified copy of the server file;

receiving, from the second client device, after the receiving of the modified copy of the server file, a second access request via the first link; and

responsive to receiving the second access request, providing a second preview representation of the modified copy of the server file to the second client device.

2. The computer-implemented method of claim 1, further comprising:

receiving, from the first client device, a request for a list of links that have been generated by the user; and

providing the first client device with the list of links.

3. The computer-implemented method of claim 1, further comprising:

receiving a second request from the first client device for a second link providing access to the server file;

responsive to receiving the second request, generating the second link specifying the server file;

distributing the first link to a first group of users and the second link to a second group of users different from the first group of users;

responsive to receiving from the user a request to revoke access via the first link, revoking access to the server file via the first link; and

after the revoking access via the first link;

permitting access to the server file via the second link to the second group of users.

4. The computer-implemented method of claim 1, wherein the first link is associated with an identifier of an application, and wherein providing the first preview representation of the server file to the second client device comprises:

identifying the application based on the identifier; and

creating the first preview representation of the server file using the application.

5. The computer-implemented method of claim 1, wherein the user interface element is a menu item within a file browser application of the first client device, and wherein selecting the user interface element comprises selecting the menu item within a menu of the file browser application.

6. The computer-implemented method of claim 1, wherein the user interface element is a web-based interface provided by the file access server.

7. The computer-implemented method of claim 1, wherein the user interface element is a link icon within a file viewing application.

8. A non-transitory computer-readable storage medium storing instructions executable by a processor, the instructions when executed performing actions comprising:

receiving, from a first client device, a request for a first link to a server file, the request received in response to a user of the first client device selecting a user interface element, the server file stored on a file access server;

responsive to receiving the request, generating the first link specifying the server file;

receiving, from a second client device different from the first client device, a first access request via the first link; and

responsive to receiving the first access request, providing a first preview representation of the server file to the second client device;

receiving a request to synchronize with the file access server, the request including a modified copy of the server file having content or metadata that is different from that of the server file stored on the file access server;

replacing the server file on the file access server with the modified copy of the server file;

receiving, from the second client device, after the receiving of the modified copy of the server file, a second access request via the first link; and

responsive to receiving the second access request, providing a second preview representation of the modified copy of the server file to the second client device.

9. The non-transitory computer-readable storage medium of claim 8, the actions further comprising:

receiving, from the first client device, a request for a list of links that have been generated by the user; and

providing the first client device with the list of links.

10. The non-transitory computer-readable storage medium of claim 8, the actions further comprising:

receiving a second request from the first client device for a second link providing access to the server file;

responsive to receiving the second request, generating the second link specifying the server file;

distributing the first link to a first group of users and the second link to a second group of users different from the first group of users;

responsive to receiving from the user a request to revoke access via the first link, revoking access to the server file via the first link; and

after the revoking access via the first link;

permitting access to the server file via the second link to the second group of users.

11. The non-transitory computer-readable storage medium of claim 8, wherein the first link is associated with an identifier of an application, and wherein providing the first preview representation of the server file to the second client device comprises:

identifying the application based on the identifier; and

creating the first preview representation of the server file using the application.

12. The non-transitory computer-readable storage medium of claim 8, wherein the user interface element is a menu item within a file browser application of the first client device, and wherein selecting the user interface element comprises selecting the menu item within a menu of the file browser application.

13. The non-transitory computer-readable storage medium of claim 8, wherein the user interface element is a web-based interface provided by the file access server.

14. The non-transitory computer-readable storage medium of claim 8, wherein the user interface element is a link icon within a file viewing application.

15. A file access server comprising;

a processor; and

a non-transitory computer-readable storage medium storing instructions executable by the processor, the instructions when executed performing actions comprising;

receiving, from a first client device, a request for a first link to a server file, the request received in response to a user of the first client device selecting a user interface element, the server file stored on the file access server;

responsive to receiving the request, generating the first link specifying the server file;

receiving, from a second client device different from the first client device, a first access request via the first link; and

responsive to receiving the first access request, providing a first preview representation of the server file to the second client device;

receiving a request to synchronize with the file access server, the request including a modified copy of the server file having content or metadata that is different from that of the server file stored on the file access server;

replacing the server file on the file access server with the modified copy of the server file;

receiving, from the second client device, after the receiving of the modified copy of the server file, a second access request via the first link; and

responsive to receiving the second access request, providing a second preview representation of the modified copy of the server file to the second client device.

16. The file access server of claim 15, the actions further comprising:

receiving, from the first client device, a request for a list of links that have been generated by the user; and

providing the first client device with the list of links.

17. The file access server of claim 15, the actions further comprising:

receiving a second request from the first client device for a second link providing access to the server file;

responsive to receiving the second request, generating the second link specifying the server file;

distributing the first link to a first group of users and the second link to a second group of users different from the first group of users;

responsive to receiving from the user a request to revoke access via the first link, revoking access to the server file via the first link; and

after the revoking access via the first link;

permitting access to the server file via the second link to the second group of users.

18. The file access server of claim 15, wherein the first link is associated with an identifier of an application, and wherein providing the first preview representation of the server file to the second client device comprises:

identifying the application based on the identifier; and

creating the first preview representation of the server file using the application.

19. The file access server of claim 15, wherein the user interface element is a menu item within a file browser application of the first client device, and wherein selecting the user interface element comprises selecting the menu item within a menu of the file browser application.

20. The file access server of claim 15, wherein the user interface element is a web-based interface provided by the file access server.