Searched hist:c66b5ec65fd5aa2f1037d2be542b49297f3aac0e (Results 1 – 5 of 5) sorted by relevance
| /dokuwiki/inc/Search/Index/ |
| H A D | Lock.php | c66b5ec65fd5aa2f1037d2be542b49297f3aac0e Sun Apr 05 17:42:37 UTC 2026 Andreas Gohr <andi@splitbrain.org> SearchIndex: rewrite Lock as static registry with reference counting
Replace the instance-based Lock class with a static registry that
tracks held locks per-process with reference counting. This solves
three problems:
- Split indexes (w3, w4, ...) share a single lock name and now
coordinate naturally via the registry
- Multiple callers can acquire the same lock without conflict
- Indexes enforce their own writability through lock()/unlock()
methods on AbstractIndex
The Lock registry manages both the filesystem lock (mkdir) and the
in-process tracking. The first acquire creates the directory, subsequent
acquires increment the refcount. Release decrements, and only removes
the directory when the count reaches zero.
Note: I am not sure if implementing this as a static object is a great
idea or if we should pass an instance through the collection to the
indexes...
|
| H A D | MemoryIndex.php | c66b5ec65fd5aa2f1037d2be542b49297f3aac0e Sun Apr 05 17:42:37 UTC 2026 Andreas Gohr <andi@splitbrain.org> SearchIndex: rewrite Lock as static registry with reference counting
Replace the instance-based Lock class with a static registry that
tracks held locks per-process with reference counting. This solves
three problems:
- Split indexes (w3, w4, ...) share a single lock name and now
coordinate naturally via the registry
- Multiple callers can acquire the same lock without conflict
- Indexes enforce their own writability through lock()/unlock()
methods on AbstractIndex
The Lock registry manages both the filesystem lock (mkdir) and the
in-process tracking. The first acquire creates the directory, subsequent
acquires increment the refcount. Release decrements, and only removes
the directory when the count reaches zero.
Note: I am not sure if implementing this as a static object is a great
idea or if we should pass an instance through the collection to the
indexes...
|
| H A D | FileIndex.php | c66b5ec65fd5aa2f1037d2be542b49297f3aac0e Sun Apr 05 17:42:37 UTC 2026 Andreas Gohr <andi@splitbrain.org> SearchIndex: rewrite Lock as static registry with reference counting
Replace the instance-based Lock class with a static registry that
tracks held locks per-process with reference counting. This solves
three problems:
- Split indexes (w3, w4, ...) share a single lock name and now
coordinate naturally via the registry
- Multiple callers can acquire the same lock without conflict
- Indexes enforce their own writability through lock()/unlock()
methods on AbstractIndex
The Lock registry manages both the filesystem lock (mkdir) and the
in-process tracking. The first acquire creates the directory, subsequent
acquires increment the refcount. Release decrements, and only removes
the directory when the count reaches zero.
Note: I am not sure if implementing this as a static object is a great
idea or if we should pass an instance through the collection to the
indexes...
|
| H A D | AbstractIndex.php | c66b5ec65fd5aa2f1037d2be542b49297f3aac0e Sun Apr 05 17:42:37 UTC 2026 Andreas Gohr <andi@splitbrain.org> SearchIndex: rewrite Lock as static registry with reference counting
Replace the instance-based Lock class with a static registry that
tracks held locks per-process with reference counting. This solves
three problems:
- Split indexes (w3, w4, ...) share a single lock name and now
coordinate naturally via the registry
- Multiple callers can acquire the same lock without conflict
- Indexes enforce their own writability through lock()/unlock()
methods on AbstractIndex
The Lock registry manages both the filesystem lock (mkdir) and the
in-process tracking. The first acquire creates the directory, subsequent
acquires increment the refcount. Release decrements, and only removes
the directory when the count reaches zero.
Note: I am not sure if implementing this as a static object is a great
idea or if we should pass an instance through the collection to the
indexes...
|
| /dokuwiki/inc/Search/Collection/ |
| H A D | AbstractCollection.php | c66b5ec65fd5aa2f1037d2be542b49297f3aac0e Sun Apr 05 17:42:37 UTC 2026 Andreas Gohr <andi@splitbrain.org> SearchIndex: rewrite Lock as static registry with reference counting
Replace the instance-based Lock class with a static registry that
tracks held locks per-process with reference counting. This solves
three problems:
- Split indexes (w3, w4, ...) share a single lock name and now
coordinate naturally via the registry
- Multiple callers can acquire the same lock without conflict
- Indexes enforce their own writability through lock()/unlock()
methods on AbstractIndex
The Lock registry manages both the filesystem lock (mkdir) and the
in-process tracking. The first acquire creates the directory, subsequent
acquires increment the refcount. Release decrements, and only removes
the directory when the count reaches zero.
Note: I am not sure if implementing this as a static object is a great
idea or if we should pass an instance through the collection to the
indexes...
|