|
From: Ed B. <Ed...@al...> - 2006-04-28 14:39:49
|
Hi, Thanks for your reply. Is it not possible to have the newest version of eAccelerator be able to decode both 5.0.x and 5.1.x since the code is already written for both? Why not look for a signature in the encoded script and call either one decoder or the other. You already have the Zend and other information in the encoded data. I was having a security issue a while back and I added an encryption step to the Turke mmcache version of the code. It put a signature in the first few bytes of the encoded script. If it didn't find that signature during decode it just bypassed the decryption step and went straight to the decoding. This would eliminate the breakage of all the previously encoded scripts. Also, this would also allow everyone to step up to your newest version without a complete recompile of all the code already written and you would get a much faster adoption of the new version. I think everyone would like to move to PHP 5.1.x at this point since 5.0.3 is from late 2004. They will just have to limit their syntax to PHP 4.3 for compiled scripts in order to keep stability until you have completed the 5.x encoder port. Then the transition will be transparent and painless and most people will already be on the new code base. BTW, I am using the encoder that came with of 0.9.2a with PHP 5.0.3 and limiting the function calls and syntax to what is available in PHP 4.3 and everything seems to work just fine. I am perfectly happy to wait for you to get the 0.9.5+ version of the encoder to support 5.x syntax. Just out of curiosity though, is there any schedule for getting the 5.x version of the encoder working? Thanks again for your input. ewb -----Original Message----- From: eac...@li... [mailto:eac...@li...] On Behalf Of Soenke Ruempler Sent: Friday, April 28, 2006 1:19 AM To: eac...@li... Subject: RE: [eAccelerator-developers] No Support for eAccelerator? Hi, eac...@li... <> wrote on : > Lastly, I attempted to build eAccelerator 0.9.4 on the machine that=20 > has PHP 5.1.2 and the build failed. Based on your statements above, I > assume it can't be built against the PHP 5.1.2 headers? > Should I regress PHP to 5.0.3 as well? Would you consider PHP 5.0.3=20 > and eAccelerator 0.9.4 a good combination for where we are? I guess, Bart wanted to point out that there is _NO_ eAccelerator with a working encoder for PHP 5.x.=20 eAccelerator 0.9.4 is stable for opcode caching of 5.0.x scripts, and 0.9.5 is for PHP 5.1.x. If you really need an encoder for PHP 5.x you'll have to consider using the commercial Zend Optimizer/Encoder. --soenke ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642 _______________________________________________ eAccelerator-developers mailing list eAc...@li... https://lists.sourceforge.net/lists/listinfo/eaccelerator-developers |