On Monday, April 16, 2012 at 5:57 PM, "Martin v. Löwis" wrote: > > Maybe a better checksum would be a global hash calculated differently ? > > > Define a protocol, and I present you with an implementation that > conforms to the protocol, and still has inconsistent data, and not > in a malicious manner, but due to bugs/race conditions/unexpected > events. It's pointless. Ultimately, clients will need to verify the > data that they receive (if they suspect issues), and fall back gracefully. > > > I can definitely see a mirroring implementation where the > > last-modified field is updated at the end while some packages are not > > copied over at the end for whatever network issue. > > > > > That mirroring implementation would violate the principle that > last-modified should only be updated when the mirroring run was > completed successfully. > >
Is this documented anywhere? I don't see it in PEP381. I agree that last-modified should only be updated when mirroring was completed successfully but I don't see that specified as part of the mirroring protocol which could lead to inconsistent definitions of what last-modified is. > > Regards, > Martin > _______________________________________________ > Catalog-SIG mailing list > Catalog-SIG@python.org (mailto:Catalog-SIG@python.org) > http://mail.python.org/mailman/listinfo/catalog-sig > >
_______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
