gallir

So, finally I added support for flock too. WP-Cache now autodetects (since version 1.5.2) if semaphores are available, if so, it uses it. Otherwise it uses flock().

It should be problems for most people now, especially those that contracted external hosting with no semaphores support.

Two things:

1. New small fix version of the plugin, 1.5.1: https://mnm.uib.es/gallir/posts/2005/03/22/200/

2. I chose semaphores because I used to them and it’s the simplest straightforward solution to the problem. I’m studying hpw to do it with flocks, but still have to see how to maintain consistency while writing two different but related files (content+meta) and also how to ensure atomicity when deleting expired files. According to some comment it seems that the ony way is to flock the directory, but I really hate this dirty tricks having a clean one.

About release notes, yes, you’re right. I will add it soon.

OTH, in the release notes of 1.0, https://mnm.uib.es/gallir/posts/2005/02/02/111/, I explain the history and how is derivated from Staticize-reloaded, I also added a trackback to the original staticize-reloaded post.

New version for WordPress 1.5, easier to install and configure:

https://mnm.uib.es/gallir/posts/2005/03/12/178/

Did you see the Wp-cache code?

Do you know it re-uses code from Staticize?

Do you is extremely optimized for WordPress?

Do you know is fun (and easy) this kind of programming?

Do you know I enjoyed programming it?

Do you know we do it for fun?

Most of the times, the problem of speed in WP is not mainly due to mysql accesess (which are very fast), but compiling the PHP code. If so, try the WP-Cache link shown above.

The above link is the article –with instructions– in English. Or at least in my English (hint: I’m Spanish).