Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What's wrong with CRC32
Message
From
08/01/2014 11:48:49
 
 
To
08/01/2014 11:40:14
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:
01591505
Views:
34
>If you resize an image, the file contents will change. It may become larger but iac the CRC has to be recalculated - file size changed or not
>
>The CRC has to be recalculated anyway - why is it important that the file size is different ?

We have 50 million records representing files on disk with their CRC32 value. On Windows Server 2003, when we resized a JPG image to 640x480, it was resulting in a smaller file in size. On Windows Server 2008, doing the same operation on the same file results in a different file size. So, we cannot identify if this file is in the database or not. We need to avoid duplicates. That worked very well until now. But, we have discovered that the OS has an impact on the file size when it is resized.

For example, Windows 7 and Windows Server 2008 resizes the file to the same file size. But, Windows 8 and Windows Server 2003 resizes the same file to a different file size, which is then different than the other environments. At first, at thought that the .NET Framework DLLs might have been updated resulted in such a change. But, this is not the case. Because, even doing it from LViewPro, on the same file, from different environments, results in the same.
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