DisabledEventIsolation
extends BaseEventIsolation
in package
FinalYes
A no-op event isolation strategy — concurrent updates are never serialised.
Ported from aiogram.fsm.storage.memory.DisabledEventIsolation
(aiogram/fsm/storage/memory.py:72-82). The upstream implementation yields
None immediately (no lock is acquired); the PHP port returns a Lock(null)
whose release() is also a no-op.
Use this as the default isolation strategy when you do not need mutual
exclusion between concurrent updates sharing the same StorageKey.
Table of Contents
Methods
- close() : void
- No-op — there are no resources to release.
- lock() : Lock
- Returns a no-op lock. No mutex is acquired; `release()` is a no-op.
Methods
close()
No-op — there are no resources to release.
public
close() : void
lock()
Returns a no-op lock. No mutex is acquired; `release()` is a no-op.
public
lock(StorageKey $key) : Lock
Parameters
- $key : StorageKey
-
Storage address to lock.