VARIANTS OF FILES IN A FILE SYSTEM

• US 20120239713A1
• Filed: 03/14/2011
• Published: 09/20/2012
• Est. Priority Date: 03/14/2011
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Velummylum, Piragash, Olson, Johanna S., Smith, Korwin J., Wood, James H.
• Granted Patent: US 8,423,585 B2
• Time in Patent Office: Days
• US Class Current: 707/822
• CPC Class Codes: G06F 16/61 Indexing; Data structures therefor; Storage structures

Abstract

Disclosed are various embodiments that provide variants of files in a file system. Multiple file systems are maintained for multiple users. Each file system includes multiple files and one or more folder. Each file includes a respective unique identifier and a respective reference to a data object stored in one or more data store. Multiple file variants are maintained. Each file variant includes the respective unique identifier of a respective file. Each file variant also includes a respective reference to a secondary data object stored in the one or more data stores. The secondary data object is related to the primary data object referenced by the respective file.

Claims

1. A non-transitory computer-readable medium embodying a program executable in at least one computing device, the program comprising:

code that maintains a plurality of file systems for a plurality of users, each of the file systems including a plurality of files and at least one folder, each of the files including a respective unique identifier and a respective reference to a primary data object stored in at least one data store;

code that obtains a request to store a file in one of the file systems from a corresponding one of the users who is associated with the one of the file systems;

code that creates a file corresponding to the file in the one of the file systems and stores a primary data object corresponding to the file in the at least one data store in response to the request;

code that encodes the file into a secondary data object that is customized for presentation on a mobile computing device associated with the corresponding one of the users and stores the secondary data object in the at least one data store;

code that creates a file variant based at least in part on the file in the corresponding file system, the file variant including a reference to the unique identifier of the file and a reference to the secondary data object stored in the at least one data store;

code that obtains a request to access the file from the corresponding one of the users;

code that sends the secondary data object referenced by the file variant to the mobile computing device when the request to access relates to access by the mobile computing device; and

code that sends the primary data object referenced by the file to another computing device when the request to access relates to access by the other computing device.

2. The non-transitory computer-readable medium of claim 1, wherein the file corresponds to an audio file, the primary data object is a version of the audio file encoded at a first bitrate, the secondary data object is a version of the audio file encoded at a second bitrate, and the first bitrate is higher than the second bitrate.

3. The non-transitory computer-readable medium of claim 1, wherein the file corresponds to an image file, the primary data object is a version of the image file encoded at a first resolution, the secondary data object is a version of the image file encoded at a second resolution, and the first resolution is higher than the second resolution.

4. A method, comprising the steps of:

maintaining, in at least one computing device, a plurality of file systems for a plurality of users, each of the file systems including a plurality of files and at least one folder, each of the files including a respective unique identifier and a respective reference to a primary data object stored in at least one data store;

generating, in the at least one computing device, a variant of one of the files, the variant including the unique identifier of the one of files and a reference to a secondary data object that relates to the primary data object referenced by the one of the files, the secondary data object being stored in the at least one data store; and

sending, in the at least one computing device, the secondary data object instead of the primary data object in response to a request for the one of the files.

5. The method of claim 4, wherein the secondary data object is derived at least in part from the primary data object.

6. The method of claim 4, wherein the request corresponds to a request to stream the one of the files over a network to a mobile computing device, and the variant is data reduced for streaming to the mobile computing device.

7. The method of claim 4, further comprising the step of obtaining, in the at least one computing device, the request for the one of the files from a client, and wherein the secondary data object is sent to the in response to the request for the one of the files.

8. The method of claim 7, wherein the client corresponds to a type of client, and the variant is customized for the type of client.

9. The method of claim 8, wherein each file system includes at least one other variant for the one of the files, and the at least one other variant is customized for at least one other type of client.

10. The method of claim 7, wherein the generating step is performed automatically before the request for the one of the files is obtained.

11. The method of claim 7, wherein the generating step is performed in response to obtaining the request for the one of the files.

12. The method of claim 7, further comprising the steps of:

determining, in the at least one computing device, the type of client;

determining, in the at least one computing device, whether the variant exists for the one of the files and the type of client; and

wherein the generating step is performed in response to determining that the variant does not exist for the one of the files and the type of client.

13. The method of claim 4, wherein each file system is associated with a corresponding one of the users.

14. A system, comprising:

at least one computing device;

a file service executable in the at least one computing device, the file service comprising;

logic that maintains a plurality of file systems for a plurality of users, each of the file systems including a plurality of files and at least one folder, each of the files including a respective unique identifier and a respective reference to a data object stored in at least one data store; and

a variant service executable in the at least one computing device, the variant service comprising;

logic that maintains a plurality of file variants, each of the file variants including the respective unique identifier of a respective one of the files, each of the file variants further including a respective reference to a secondary data object stored in the at least one data store that relates to the respective primary data object referenced by the respective one of the files.

15. The system of claim 14, wherein the variant service further comprises:

logic that associates a type of client with one of the users; and

logic that generates at least one of the file variants in response to the type of client being associated with the one of the users, the at least one of the file variants being customized for the type of client.

16. The system of claim 15, wherein the variant service further comprises:

logic that determines whether the type of client remains associated with the one of the users; and

logic that initiates a deletion of the at least one of the file variants in response to determining that type of client does not remain associated with the one of the users.

17. The system of claim 14, wherein the variant service further comprises:

logic that determines a type of client associated with a request for at least one of the files; and

logic that generates at least one of the file variants in response to the request, the at least one of the file variants being customized for the type of client.

18. The system of claim 14, wherein at least one of the file variants includes a unique identifier of one of the file variants in place of the respective unique identifier of the respective one of the files.

19. The system of claim 14, wherein the variant service further comprises logic that generates one of the secondary data objects by encoding the corresponding one of the primary data objects with an encoder.

20. The system of claim 19, wherein the encoder includes an audio codec.

21. The system of claim 19, wherein the corresponding one of the primary data objects is an image, and the one of the secondary data objects is a reduced size version of the image.