Changes between Version 4 and Version 5 of Introduction

Timestamp:

2006-06-04T13:32:09+02:00 (9 years ago)

Author:

moo

Comment:

thanks Steve, and sorry for my misleading :P

Introduction

@@ -3 +3 @@
 XCache is a open-source opcode cacher, which means that it accelerates the performance of PHP on servers. It optimizes performance by removing the compilation time of PHP scripts by caching the compiled state of PHP scripts into the shm (RAM) and uses the compiled version straight from the RAM. This will increase the rate of page generation time by up to 5 times as it also optimizes many other aspects of php scripts and reduce serverload.
 
-The XCache project is lead by Moo who is also a developer of Lighttpd. Lighttpd is one of the fastest webserver programs and outperforms Apache and many other open source webserving projects so the same is being done to XCache.
+The XCache project is lead by mOo who is also a developer of Lighttpd. Lighttpd is one of the fastest webserver programs and outperforms Apache and many other open source webserving projects so the same is being done to XCache.
 
 == Do you (the author of XCache) know [http://pecl.php.net/apc apc], [http://eaccelerator.sf.net eaccelerator], [http://www.php-accelerator.co.uk/ phpa], [http://turck-mmcache.sourceforge.net/index_old.html truck-mmcache] ? ==
 Yeah, i know them very well.
 
-I've noticed phpa (PHP Accelerator) long ago, the time while truck-mmcache is still under maintained actively. But saidly phpa's project died and never updated it's code to support newly released versions of PHP. So i used truck-mmcache for a period of time, but... it hang or crash continously after being under high load. I noticed APC later, but I've been reading both APC/truck-mmcache] source for a long time (I can't write XCache if haven't read them), discovering that APC code is simpler and beautiful than mmcache's. So I finally turned to APC's code to base XCache on. mmcache forked eaccelerator, and they setup [http://www.eaccelerator.net www.eaccelerator.net], running [http://trac.edgewall.com/ trac].
+I've noticed phpa (PHP Accelerator) long ago, the time while truck-mmcache is still under maintained actively. But saidly phpa's project died and never updated it's code to support newly released versions of PHP. So i used truck-mmcache for a period of time, but... it hang or crash continously after being under high load. I noticed APC later, but I've been reading both APC/truck-mmcache source for a long time (I can't write XCache if haven't read them), discovering that APC code is simpler and beautiful than mmcache's. Features are good, but i believe the stability is more important. So I finally turned to run APC online -- simpler often means more stable. mmcache forked eaccelerator later, and they setup [http://www.eaccelerator.net www.eaccelerator.net], running [http://trac.edgewall.com/ trac].
 
 == But why do you write XCache after that? Why not contribute to ea/apc? ==