tiker
02-18-2004, 06:49 AM
Not sure if this is a problem, but in theory it could be.
When running the packet collector, it stores the data it's collected in the file on the hard drive. When it's launched for the first time, it loads the data from the file, and uploads all entries the first time until they're flagged as sent in memory. From another thread on the forums here, someone said it does a MD5 checksum compare with the server and if they're different, the local copy is sent to the server.
Here's the question: If the details of an item is changed and uploaded by a person, would the version I have on my system which is not the updated version get uploaded to the server because the MD5 checksum is different when I do the first upload with the client causing the updated version on the server to revert back to the old version?
Couldn't there be some sort of programming default set to say if the item is loaded from disk, not to try and upload it again unless it's changed?
When running the packet collector, it stores the data it's collected in the file on the hard drive. When it's launched for the first time, it loads the data from the file, and uploads all entries the first time until they're flagged as sent in memory. From another thread on the forums here, someone said it does a MD5 checksum compare with the server and if they're different, the local copy is sent to the server.
Here's the question: If the details of an item is changed and uploaded by a person, would the version I have on my system which is not the updated version get uploaded to the server because the MD5 checksum is different when I do the first upload with the client causing the updated version on the server to revert back to the old version?
Couldn't there be some sort of programming default set to say if the item is loaded from disk, not to try and upload it again unless it's changed?