Ensure thread-safety about python-tuf HOT 4 CLOSED

I vote for a global lock for expediency.

On Tue, Mar 19, 2013 at 2:17 AM, TKK [email protected] wrote:

Presently, there is no thread-safety for some important things, such as:

• Switching tuf.conf global configuration variables between different
  TUF clients.
• Downloading the same target files with the same TUF client.

—
Reply to this email directly or view it on GitHubhttps://github.com/akonst/tuf/issues/49
.

from python-tuf.

I wonder whether we would like to extend concurrence-safety to the repository tools (e.g. making a delegation).

Why would we want this? Well, suppose a developer wants to generate TUF metadata for tens of thousands of packages. It would be nice if she could parallelize her automation without worrying about whether the TUF repository tools would be concurrence-safe (e.g. ensuring that the parent/delegator metadata is safely updated).

Anyway, even if we wanted to do this, it would be at the end of our priority queue.

from python-tuf.

Quick fix: Note in the readme that TUF might behave unexpectedly when concurrently downloading from the same location to the same location.

from python-tuf.

#972 added an explanation of this limitation to the readme.

from python-tuf.