Abstract: Technologies for detecting changes in a namespace using namespace enumeration endpoint response payloads are disclosed. A namespace is enumerated at a first time by retrieving response payloads containing metadata describing each location in the namespace from a namespace enumeration endpoint. Signatures are generated based on the response payloads and stored. To determine if changes were made to the namespace between the first time and a subsequent second time, metadata is retrieved from the namespace enumeration endpoint for the namespace at the second time and signatures are generated. Signatures generated at the first time are then compared to the signatures generated at the second time. If the signatures are different, the items in the location in the namespace changed between the first time and the second time. Changes occurring in a location of the namespace can then be identified based on the metadata obtained at the first and second times.

Abstract: Technologies for detecting changes in a namespace using namespace enumeration endpoint response payloads are disclosed. A namespace is enumerated at a first time by retrieving response payloads containing metadata describing each location in the namespace from a namespace enumeration endpoint. Signatures are generated based on the response payloads and stored. To determine if changes were made to the namespace between the first time and a subsequent second time, metadata is retrieved from the namespace enumeration endpoint for the namespace at the second time and signatures are generated. Signatures generated at the first time are then compared to the signatures generated at the second time. If the signatures are different, the items in the location in the namespace changed between the first time and the second time. Changes occurring in a location of the namespace can then be identified based on the metadata obtained at the first and second times.