File tree Expand file tree Collapse file tree 1 file changed +5
-6
lines changed Expand file tree Collapse file tree 1 file changed +5
-6
lines changed Original file line number Diff line number Diff line change @@ -161,12 +161,6 @@ a lock, you can use the ``isAcquired()`` method::
161
161
// We (still) own the lock
162
162
}
163
163
164
-
165
- .. [1 ] Technically, the true owners of the lock are the ones that share the same instance of ``Key ``,
166
- not ``Lock ``. But from a user perspective, ``Key `` is internal and you will likely only be working
167
- with the ``Lock `` instance so it's easier to think of the ``Lock `` instance as being the one that
168
- is the owner of the lock.
169
-
170
164
Because of the fact that some lock stores have expiring locks (as seen and explained
171
165
above), it is possible for an instance to lose the lock it acquired automatically::
172
166
@@ -196,6 +190,11 @@ above), it is possible for an instance to lose the lock it acquired automaticall
196
190
you have to use ``acquire() `` for this. The ``isAcquired() `` method is used to check
197
191
if the lock has been acquired by the **current process ** only!
198
192
193
+ .. [1 ] Technically, the true owners of the lock are the ones that share the same instance of ``Key ``,
194
+ not ``Lock ``. But from a user perspective, ``Key `` is internal and you will likely only be working
195
+ with the ``Lock `` instance so it's easier to think of the ``Lock `` instance as being the one that
196
+ is the owner of the lock.
197
+
199
198
Available Stores
200
199
----------------
201
200
You can’t perform that action at this time.
0 commit comments