[TYPO3-core] RFC: Bug #7630: Locking Problems with TSFE->set_no_cache()

Jeff Segars jsegars at alumni.rice.edu
Mon Feb 25 15:47:54 CET 2008


Oliver Hader wrote:
>  Releasing locks in $TSFE->set_no_cache() is one possibility, but if
> an extension just sets $TSFE->no_cache=1 it won't help. I tend to
> always check for and release the locks even if caching was disabled
> at the 
>  beginning.

>  Please have look to my attachment which solves the following:
>  * always release aquired locks, no matter if no_cache is set
>  * always remove (additional to release) semaphores to prevent leaks
> For further details see the post discussion of RFC #7333 in the
> bugtracker [1].

>  What do you think?

Thanks Olly.  Sounds like a better solution than mine.  I just
discovered the issue right before beta2 and didn't realize you were
already looking at it :)  I'll test the patch later today, but from
reading I'm confident it will work.

Thanks,
Jeff




More information about the TYPO3-team-core mailing list