SCUP's Catalog update detection process


SCUP will detect when third-party catalog files (that it knows about) are updated. Here is the behavior for SCUP when checking for updated catalogs.
  1. SCUP first looks for the signature file (*.xml file)
  2. If file is present it looks at the hash value and compares it to what is in the SCUP database
  3. If the hash doesn’t match it will add it to the Catalog Update list (center bottom of SCUP console)
  4. If has does match it will leave it off of Catalog Update list
  5. If signature file is missing it will then download cab file and crack open
  6. A hash will be created based off the catalog file and compared to the database
  7. If the hash doesn’t match it will add it to the Catalog Update list (center bottom of SCUP console)
  8. If has does match it will leave it off of Catalog Update list

So even if the signature file is missing this feature should work, but will take longer as it has to download the much bigger catalog file. If there is any issues downloading the catalog, then the item should be inserted into the catalog update list with red colored font.

This is why it is important to keep a copy of the "un-cabbed" catalog XML file in the same location as the CAB file for your catalog.

Last edited Aug 10, 2009 at 7:44 PM by rhearn, version 1

Comments

No comments yet.