download marker used for container and object listings
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-swiftclient |
New
|
Undecided
|
Unassigned | ||
Bug Description
In the "download" command, one may specify an initial marker (--marker or -m).
However, that marker value is used when iterating over containers in the account ("-a" also specified) as well as when iterating over each container's objects. It seems like any single initial marker value could only be valid for one of those two.
The proper fix depends on the desired semantics of "--marker", and I don't know exactly why it was originally added. I can think of a few ways to go on this:
1) Split --marker into two options, --container-marker and --object-marker, both defaulting to '' (empty-string). Then, --container-marker would only be used when iterating over the account's containers and --object-marker would be used when iterating over every containers' objects.
2) Make --marker only apply to iterating over containers' objects. The iteration over the account's containers would always start with a marker value of '' (empty-string).
3) Make --marker only get used for the first iteration done. If "-a" is specified, then --marker would only initialize the marker value for the iteration of the account's containers. Every containers' objects would be listed starting with an initial marker value of '' (empty-string). Without "-a", --marker would be used as the initial marker value for iterating over the container's objects.
4) Leave it alone. I misunderstood the desired semantics, and whenever --marker is specified with "-a", the initial marker *should* be applied for iterating the account's containers and each containers' objects.
Thoughts? I think fix #1 or #2 would be best, depending on the originally-desired semantics.
