Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Make it harder to use file locking because it's not really needed. #174
The plugin writes to files with random filenames and then renames those
The plugin writes to files with random filenames and then renames those files to their final cached filename which is an atomic action that can't be interupted. The only reason to have this coarse locking is if your server is so underpowered it can't cope with multiple processes writing to files at the same time. This will slow down how fast new files are cached significantly. This patch changes the language on the settings page warning the user that if will slow down their website. The cosnstant "WPSC_DISABLE_LOCKING" was used to hide the setting, but now it's checked in each function that implements file locking. sem_remove() seems to cause problems using semaphores so it is disabled unless the constant "WPSC_REMOVE_SEMAPHORE" is defined.
* Don't delete so many files on blogs with static homepages. #175 * Discourage use of file locking because semaphores cause problems and it's not needed. #174 * Reorganise the settings page in small ways #173 * Fixed XSS in settings page. Props @jaypatel #172 git-svn-id: http://plugins.svn.wordpress.org/wp-super-cache/trunk@1587563 b8457f37-d9ea-0310-8a92-e5e31aec5664