I hit the wrong reply option previously. Sorry for the duplicate in private, Brian.
I see this pretty rarely. It's normally the length of the file in bytes. I think we're overthinking this. I had originally suggested to William that comparing the timestamps and length would be a super inexpensive way to determine conclusively we needed to download the file without having to download the hash file and do a hash locally. Obviously, if all of those indicators agree, we'd need to do that anyway. If the math is too hard, just hash it each time. On Wednesday, January 8, 2014 11:35:53 AM UTC-8, Brian Coca wrote: > > File sizes can be tricky, most systems report how much the file occupies, > which is normally larger than the exact bit count of the file itself (be it > fs blocks, packets or encoded base64/mime encapsulated/armored/etc). > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
