Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What's wrong with CRC32
Message
From
08/01/2014 13:33:50
 
 
To
08/01/2014 13:28:37
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01591437
Message ID:
01591521
Views:
36
>Then either
>(1) Always overwrite, or
>(2) Assume the original ones had a zero checksum. The next one you receive calculate the checksum, it will be different, hence store the new checksum, resize, store the resized image
>
>So an identical image will only be replaced the first time
>
>Looks like an easy transition from the old system to the new one

Yes, this is what we are doing. We can only have it from the date we migrated and then on.

It just surprised me that so many people recommended to use CRC32 when from OS to OS, this may change because the file size of a file might not be stored the same way when changing OS.

The only way I could see a good usage of CRC32 is to detect something immediate but not to store it on a permanent basis so to rely on it for months and years to come.

For now, while we have kept the storage of the CRC32, we have changed the detection of similar files by checking the file name as this is something that the incoming source is controlling and there shouldn't be two files with the same names representing the same content.
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform