I really don't see why expired objects are such a special case that they need to be solved? Anytime you iterate over a listing of objects from a container there is a chance that one of those objects may 404 for a number of reasons.
Is there an application level problem that simply can't account for a container listing being out of sync with the objects? Maybe there's a more general way to deal approach the problem that better jives with "eventual consistency"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
