http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-05-06T21:00:51ZTYPO3 ForgeTYPO3 Core - Feature #88279: Implement SemaphoreLockStrategy as LOCK_CAPABILITY_NOBLOCK by using $nowait parameter of sem_acquire()http://forge.typo3.org/issues/88279?journal_id=3995882019-05-06T21:00:51ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>Thanks for your report.</p>
<p>Unfortunately this is only half of the truth.<br />The noWait option is not implemented like it is usually on system level. Setting it to true will cause the function to return false if the lock couldn't be acquired.<br />Unfortunately there seems to be no way to distinguish between a failed locking attempt (system related) or because it would block.</p>
<p>This is the reason why I didn't implement the noWait feature into the core's API.<br />Other means of locking allow to distinguish properly between "WOULD BLOCK" and an error.</p> TYPO3 Core - Feature #88279: Implement SemaphoreLockStrategy as LOCK_CAPABILITY_NOBLOCK by using $nowait parameter of sem_acquire()http://forge.typo3.org/issues/88279?journal_id=4070532019-10-01T20:11:16ZChristian Eßl
<ul><li><strong>Category</strong> set to <i>Locking / Session Handling</i></li></ul> TYPO3 Core - Feature #88279: Implement SemaphoreLockStrategy as LOCK_CAPABILITY_NOBLOCK by using $nowait parameter of sem_acquire()http://forge.typo3.org/issues/88279?journal_id=4070792019-10-01T21:30:18ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Rejected</i></li></ul>