public interface RWLock extends Lock
| Modifier and Type | Method and Description |
|---|---|
boolean |
isRLocked()
Checks whether this lock is reader-locked (or has reached the max lock holders)
|
Mono<Void> |
rLock()
Deprecated.
Use
withRLock(Supplier) to handle cancelling signals
The difference is that the underlying implementation might choose to implement a Readers–writer lock.
Do not use |
<T> Mono<T> |
rLockOnNext(Mono<T> mono)
Deprecated.
Use
withRLock(Supplier) to handle cancelling signals
The difference is that the underlying implementation might choose to implement a Readers–writer lock. |
void |
rUnlock()
See
Lock.unlock() for details. |
<T> Mono<T> |
rUnlockOnEmpty(Mono<T> mono)
Deprecated.
Use
withRLock(Supplier) to handle cancelling signals |
<T> Mono<T> |
rUnlockOnError(Mono<T> mono)
Deprecated.
Use
withRLock(Supplier) to handle cancelling signals |
<T> Mono<T> |
rUnlockOnNext(Mono<T> mono)
Deprecated.
Use
withRLock(Supplier) to handle cancelling signals |
<T> Mono<T> |
rUnlockOnTerminate(Mono<T> mono)
Deprecated.
Use
withRLock(Supplier) to handle cancelling signals |
LockHandle |
tryRLock()
The reader lock equivalent to
Lock.tryLock() |
Mono<Void> |
tryRLock(Duration duration)
Deprecated.
Use
Lock.withLock(Supplier) to handle cancelling signals |
<T> Flux<T> |
withRLock(Supplier<Publisher<T>> scoped)
The reader lock version of
Lock.withLock(Supplier). |
begin, isLocked, lock, lockOnNext, tryLock, tryLock, unlock, unlockOnEmpty, unlockOnError, unlockOnNext, unlockOnTerminate, withLockLockHandle tryRLock()
Lock.tryLock()
See LockHandle and Lock.tryLock()
@Deprecated Mono<Void> tryRLock(Duration duration)
Lock.withLock(Supplier) to handle cancelling signalsTimeoutException
downstream after certain duration.duration - the time to wait for lockMono that emits success when the lock is acquired<T> Flux<T> withRLock(Supplier<Publisher<T>> scoped)
Lock.withLock(Supplier).@Deprecated Mono<Void> rLock()
withRLock(Supplier) to handle cancelling signals
The difference is that the underlying implementation might choose to implement a Readers–writer lock.
Do not use Mono.timeout(Duration) or Mono.timeout(Publisher),
which are not handled at all. Use tryRLock(Duration) or tryRLock() instead
if you want timeouts.
AbstractLock.lock() for details.Mono that emits success when the lock is acquiredboolean isRLocked()
You should not rely on the result of this due to possible concurrent operations.
@Deprecated <T> Mono<T> rLockOnNext(Mono<T> mono)
withRLock(Supplier) to handle cancelling signals
The difference is that the underlying implementation might choose to implement a Readers–writer lock.
void rUnlock()
Lock.unlock() for details.@Deprecated <T> Mono<T> rUnlockOnEmpty(Mono<T> mono)
withRLock(Supplier) to handle cancelling signalsAbstractLock.unlockOnEmpty(Mono) for details.@Deprecated <T> Mono<T> rUnlockOnNext(Mono<T> mono)
withRLock(Supplier) to handle cancelling signalsAbstractLock.unlockOnNext(Mono) for details.@Deprecated <T> Mono<T> rUnlockOnTerminate(Mono<T> mono)
withRLock(Supplier) to handle cancelling signalsAbstractLock.unlockOnTerminate(Mono) for details.@Deprecated <T> Mono<T> rUnlockOnError(Mono<T> mono)
withRLock(Supplier) to handle cancelling signalsAbstractLock.unlockOnError(Mono) for details.