Changes between Version 2 and Version 3 of Introduction


Ignore:
Timestamp:
2006-06-02T22:28:11+02:00 (8 years ago)
Author:
Steve
Comment:

Fixed some grammar errors.

Legend:

Unmodified
Added
Removed
Modified
  • Introduction

    v2 v3  
    99I DID filing bug report, submiting patches to both [http://pecl.php.net/bugs/search.php?cmd=display&package_name[]=APC&status=All apc bug report system] and [http://sourceforge.net/tracker/?group_id=69426&atid=524487 truck-mmcache on sf.net] and interactive with communicate with [http://blog.zoeloelip.be/ zoeloelip], one of the main [https://sourceforge.net/users/zoeloelip/ developer] of eaccelerator. He's the first one read my XCache source, long before XCache is published online. I'm not sure, but i guess the idea he rewrite ea_dasm.c is base on my Disassembler idea in XCache :) 
    1010 
    11 There's many reason make me to write XCache instead of keeping patching ea/apc. 
     11There are many reasons for me to write XCache instead of using APC or EA: 
    1212 * Something too big to be made into them (ea/apc). 
    1313 * I have many new ideas on opcode cacher, but i just can't break their cacher to prove my ideas. 
    14  * To prove my programming skill? Making project oneself isn't that simple. With only programming skill is far insufficient, you need to become project admin, designing how the project will be, foresee the cost and benefits ... blah blah 
     14 * To prove my programming skills? Making project oneself isn't that simple. With only programming skill is far insufficient, you need to become project admin, designing how the project will be, foresee the cost and benefits ... blah blah 
    1515 
    16 And a final episode: I had written XCache for a long time before I have apc online for a long time. it's quite stable for php4, using flock(), so why I switch? I didn't. The only reason i switch is that apc stop working when then time I upgrade my server to dual cpu(4 threaded cpu at total), it flock()s deadly. It is said fixed after i switch to XCache, good news anyway. 
     16To conclude, I've finished writting XCache for quite a long time, before then I had used APC. Although it was quite stable for a php4 with flock() configuration it had become unstable once I upgraded my server to a dual cpu (4 threaded cpu) because it flock()ed badly so XCache was used instead and seems to have solved the problem. 
    1717 
    1818ea/apc is still good opcode cacher, as long as it's maintained actively, and if it's stable for you.