-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure thread-safety #49
Comments
I vote for a global lock for expediency. On Tue, Mar 19, 2013 at 2:17 AM, TKK notifications@github.com wrote:
|
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. |
Quick fix: Note in the readme that TUF might behave unexpectedly when concurrently downloading from the same location to the same location. |
#972 added an explanation of this limitation to the readme. |
Presently, there is no thread-safety for some important things, such as:
tuf.conf
global configuration variables between different TUF clients.The text was updated successfully, but these errors were encountered: