Project

General

Profile

Actions

Feature #18557

closed

Integrate locking by database in t3lib_lock

Added by Oliver Hader over 16 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
Category:
Locking / Session Handling
Target version:
-
Start date:
2008-04-03
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.2
Tags:
Complexity:
Sprint Focus:

Description

In environments with more than one webserver, locking on using the filesystem might not be a good idea since synchronisation of those information is too slow. A possibility is to use the database storage for locking.
This issue is not about database transactions but more about storing a locking semaphore in the database.

A new locking mode besides simple, flock, semaphore and disable shall be integrated: <b>database</b>

(issue imported from #M8010)


Files

oracle__typo3_dbLock.zip (933 Bytes) oracle__typo3_dbLock.zip Administrator Admin, 2008-04-03 18:08
0008010.patch (4.71 KB) 0008010.patch Administrator Admin, 2008-04-03 18:14
0008010_v2.patch (2.9 KB) 0008010_v2.patch Administrator Admin, 2008-04-21 14:43
0008010_v3.patch (4.12 KB) 0008010_v3.patch Administrator Admin, 2010-07-21 16:40

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #24342: t3lib_lock still sometimes has a race condition on deleting locks.Closed2010-12-15

Actions
Actions

Also available in: Atom PDF