Skip to content

Update lockable_trait.rst for blocking lock #8076

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

Merged
merged 2 commits into from
Jul 7, 2017
Merged

Update lockable_trait.rst for blocking lock #8076

merged 2 commits into from
Jul 7, 2017

Conversation

lpussacq
Copy link
Contributor

The method lock() of LockableTrait accept 2 parameters, the first one is the name used to create the lock file, and the second is a value indicating if we should wait until the lock is release. Thus, the line $this->lock(true); should be $this->lock('someRandomLockName', true);

The method lock() of LockableTrait accept 2 parameters, the first one is the name used to create the lock file, and the second is a value indicating if we should wait until the lock is release. Thus, the line $this->lock(true); should be $this->lock('someRandomLockName', true);
@@ -30,7 +30,7 @@ that adds two convenient methods to lock and release commands::
}

// If you prefer to wait until the lock is released, use this:
// $this->lock(true);
// $this->lock('lockname', true);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about passing null as the first argument instead to use the default lock name?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

null could do the trick as any string. Using null result in using the name define for the command. My point is to use the blocking functionnality of the trait, we need to add a first parameter before true.

Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've made the change requested by @xabbuh to move faster and make this mergeable.

By the way, now that we have the Lock component, I wonder if we should keep using this LockableTrait.

@xabbuh
Copy link
Member

xabbuh commented Jul 7, 2017

Thank you @lpussacq.

@xabbuh xabbuh merged commit 7c99b93 into symfony:3.2 Jul 7, 2017
xabbuh added a commit that referenced this pull request Jul 7, 2017
…viereguiluz)

This PR was merged into the 3.2 branch.

Discussion
----------

Update lockable_trait.rst for blocking lock

The method lock() of LockableTrait accept 2 parameters, the first one is the name used to create the lock file, and the second is a value indicating if we should wait until the lock is release. Thus, the line $this->lock(true); should be $this->lock('someRandomLockName', true);

Commits
-------

7c99b93 Use "null" so the lock is named automatically
615817e Update lockable_trait.rst
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants