Difference between revisions of "Asset"
From YTMND
Alphasuede (Talk | contribs) (Needs a lot of work still... Created a page on Asset. Unsure how the asset id is differernt than the md5) |
Alphasuede (Talk | contribs) m (spelling fix) |
||
| Line 1: | Line 1: | ||
| − | An asset ID refers to a unique ID of every YTMND image and sound file | + | An asset ID refers to a unique ID of every YTMND image and sound file. |
| − | + | ||
| − | + | * Like many multimedia hosting sites, YTMND uses the md5 cryptographic hash function to compute a unique filename for every sound and image uploaded to the servers. | |
| + | * It is unclear if the asset ID refers to the md5 code of the file or another number. | ||
| − | MD5 hash codes are 128 bit values represented as 32 character strings. | + | * MD5 hash codes are 128 bit values represented as 32 character strings. |
When a user creates a site and uploads a file, the server computes the md5 hash checks if any previously uploaded file file's name exists with an identical hash code. | When a user creates a site and uploads a file, the server computes the md5 hash checks if any previously uploaded file file's name exists with an identical hash code. | ||
| − | This prevents duplicate files without having to resort to bit by bit comparisons of every file. What a computational bargain! However there is a very rare possibility of two different files having a hash collision. In this case, the YTMND author should slightly modify the offending file and re-upload. It is unknown if this has ever happened on ytmnd. | + | * This prevents duplicate files without having to resort to bit by bit comparisons of every file. What a computational bargain! However there is a very rare possibility of two different files having a hash collision. In this case, the YTMND author should slightly modify the offending file and re-upload. It is unknown if this has ever happened on ytmnd. |
| − | In any case, once a file is uploaded it is stored as with a filename and path based on the md5. | + | * In any case, once a file is uploaded it is stored as with a filename and path based on the md5. |
{{stub}} | {{stub}} | ||
Revision as of 01:25, June 15, 2009
An asset ID refers to a unique ID of every YTMND image and sound file.
- Like many multimedia hosting sites, YTMND uses the md5 cryptographic hash function to compute a unique filename for every sound and image uploaded to the servers.
- It is unclear if the asset ID refers to the md5 code of the file or another number.
- MD5 hash codes are 128 bit values represented as 32 character strings.
When a user creates a site and uploads a file, the server computes the md5 hash checks if any previously uploaded file file's name exists with an identical hash code.
- This prevents duplicate files without having to resort to bit by bit comparisons of every file. What a computational bargain! However there is a very rare possibility of two different files having a hash collision. In this case, the YTMND author should slightly modify the offending file and re-upload. It is unknown if this has ever happened on ytmnd.
- In any case, once a file is uploaded it is stored as with a filename and path based on the md5.
- This page is a stub. Make it meaningful and add something to it.
