currently ETag values are created using a file hash that's stored in an internal dictionary forever. This will cause memory issues if left to expand and so needs to be updated to use caching and pulling ETag values from S3 where possible instead of generating on the fly
currently ETag values are created using a file hash that's stored in an internal dictionary forever. This will cause memory issues if left to expand and so needs to be updated to use caching and pulling ETag values from S3 where possible instead of generating on the fly